Triple
T28307
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indo-European language family |
E564
|
entity |
| Predicate | timeDepth |
P302
|
FINISHED |
| Object | late Neolithic to early Bronze Age (hypothesized) |
—
|
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: late Neolithic to early Bronze Age (hypothesized) | Statement: [Indo-European language family, timeDepth, late Neolithic to early Bronze Age (hypothesized)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeDepth Context triple: [Indo-European language family, timeDepth, late Neolithic to early Bronze Age (hypothesized)]
-
A.
timePeriod
chosen
Indicates the specific span or interval of time during which an event, state, or relationship occurs or is valid.
-
B.
depthRank
Indicates the relative ordering of entities based on how deep or distant they are along a specified depth dimension or hierarchy.
-
C.
maximumDepth
Indicates the greatest extent or deepest level reached by something within a given context or structure.
-
D.
hasAverageDepth
Indicates that an entity possesses a specified mean depth value, typically measured over its entire extent or area.
-
E.
tempo
Indicates the speed or pace at which an action, process, or sequence unfolds over time.
- 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_69a2479dec388190967ba648663442c9 |
completed | Feb. 28, 2026, 1:40 a.m. |
| NER | Named-entity recognition | batch_69a24925607c8190a9ce7ec834f3e5bb |
completed | Feb. 28, 2026, 1:47 a.m. |
| PD | Predicate disambiguation | batch_69a2486bd74c81908d32be3c7d22f51f |
completed | Feb. 28, 2026, 1:44 a.m. |
Created at: Feb. 28, 2026, 1:44 a.m.