Triple
T22116703
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oldowan stone tools |
E546562
|
entity |
| Predicate | technologicalComplexity |
P2086
|
FINISHED |
| Object | relatively simple |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: relatively simple | Statement: [Oldowan stone tools, technologicalComplexity, relatively simple]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: technologicalComplexity Context triple: [Oldowan stone tools, technologicalComplexity, relatively simple]
-
A.
technologyLevel
chosen
Indicates the degree of technological advancement or sophistication associated with an entity relative to others or to a defined scale.
-
B.
technologyLevelComparedTo
Indicates how the technological advancement of one entity compares relative to that of another entity.
-
C.
technologyReadiness
Indicates the level to which a technology has been developed, tested, and proven ready for practical or operational use.
-
D.
isMoreTechnicalThan
Indicates that one entity possesses a higher level of technical complexity, expertise, or specialization than another entity.
-
E.
technologicalFeature
Indicates that one entity possesses, exhibits, or is characterized by a specific technological capability, component, or functionality in relation to another entity.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69e11e38b3848190ac3a4fa97d56e65a |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f1294e85708190b455846bacbdfd03 |
completed | April 28, 2026, 9:40 p.m. |
| PD | Predicate disambiguation | batch_69e71b2ed7348190b6fa2e52f54393fb |
completed | April 21, 2026, 6:37 a.m. |
Created at: April 16, 2026, 8:31 p.m.