Triple
T9159033
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lindenmeier site |
E219774
|
entity |
| Predicate | radiocarbonAge |
P52881
|
FINISHED |
| Object | approximately 10,800–10,000 years BP |
—
|
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: approximately 10,800–10,000 years BP | Statement: [Lindenmeier site, radiocarbonAge, approximately 10,800–10,000 years BP]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: radiocarbonAge Context triple: [Lindenmeier site, radiocarbonAge, approximately 10,800–10,000 years BP]
-
A.
radiocarbonDatingPerformed
Indicates that radiocarbon dating has been carried out on an entity to determine its age or time period.
-
B.
approximateAgeBeforePresent
chosen
Indicates that one entity’s age is an estimated value measured as a time interval before the present moment.
-
C.
archaeologicalEvidenceAge
Indicates the age or time period to which a piece of archaeological evidence is dated.
-
D.
geochronologyMethod
Indicates the method or technique used to determine the age or chronological sequence of geological materials or events.
-
E.
estimatedAgeInMillionsOfYears
Indicates the approximate age of something expressed in units of millions of years.
- 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_69ca83e3633c81908688a9fa2306ba99 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cca9d805588190a0deadda1dd410a1 |
completed | April 1, 2026, 5:15 a.m. |
| PD | Predicate disambiguation | batch_69cc6605c6808190a30d92da006206ac |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:21 p.m.