Triple
T3175840
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stone Age |
E66462
|
entity |
| Predicate | mainTechnology |
P28887
|
FINISHED |
| Object | knapped stone tools |
—
|
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: knapped stone tools | Statement: [Stone Age, mainTechnology, knapped stone tools]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainTechnology Context triple: [Stone Age, mainTechnology, knapped stone tools]
-
A.
mainGenerationTechnology
chosen
Indicates the primary technology or method used to generate something, typically identifying the dominant production or generation approach among possible alternatives.
-
B.
technologyBasis
Indicates that one entity is founded on, enabled by, or fundamentally relies upon the technology provided or represented by another entity.
-
C.
technologyType
Indicates the specific kind or category of technology associated with an entity or relationship.
-
D.
laterUsedTechnology
Indicates that one entity adopted or employed a technology after another entity had already used it.
-
E.
technologyField
Indicates the area or domain of technology in which an entity is involved, specialized, or categorized.
- 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_69ad8586a34c8190944c63ec11a8de1a |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada671e6848190a683eec1519b9268 |
completed | March 8, 2026, 4:40 p.m. |
| PD | Predicate disambiguation | batch_69ad9e02677c8190a21d93b1259b2761 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:06 p.m.