Triple
T1966383
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Columbia |
E42696
|
entity |
| Predicate | approximateAssemblyAgeMa |
P16042
|
FINISHED |
| Object | 2100 |
—
|
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: 2100 | Statement: [Columbia, approximateAssemblyAgeMa, 2100]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateAssemblyAgeMa Context triple: [Columbia, approximateAssemblyAgeMa, 2100]
-
A.
estimatedAgeInMillionsOfYears
chosen
Indicates the approximate age of something expressed in units of millions of years.
-
B.
geologicalAge
Indicates the time period in Earth's geological history during which an entity (such as a rock, fossil, or formation) originated or was formed.
-
C.
estimatedYearOfCreation
Indicates the year in which something is believed or approximated to have been created, rather than a precisely known creation year.
-
D.
archaeologicalEvidenceAge
Indicates the age or time period to which a piece of archaeological evidence is dated.
-
E.
approximateAgeAtDeath
Indicates the estimated age a person or entity was when they died, typically used when the exact age is unknown.
- 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_69a88711151c8190940b2572095059d7 |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb3cd47388190998b5f6800141c92 |
completed | March 7, 2026, 5:12 a.m. |
| PD | Predicate disambiguation | batch_69abaff7d4a48190ab0d51aefb1c4e31 |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:36 p.m.