Triple
T25455461
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Niah Caves |
E637901
|
entity |
| Predicate | earliestHumanRemainsAge |
P86845
|
FINISHED |
| Object | about 40,000 years |
—
|
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: about 40,000 years | Statement: [Niah Caves, earliestHumanRemainsAge, about 40,000 years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: earliestHumanRemainsAge Context triple: [Niah Caves, earliestHumanRemainsAge, about 40,000 years]
-
A.
archaeologicalEvidenceAge
Indicates the age or time period to which a piece of archaeological evidence is dated.
-
B.
earliestCultEvidence
Indicates the earliest known archaeological or historical evidence for the existence of a particular cult or organized worship practice.
-
C.
earliestHumanPresenceIn
chosen
Indicates the time or event corresponding to the first known occurrence of humans being present in a given place or region.
-
D.
earliestFindsDateTo
Indicates the earliest known date at which the finding, discovery, or observation of one entity is recorded as relating to another entity.
-
E.
earliestKnownAncestor
Indicates that one entity is the most distant (oldest) known ancestor in the lineage of 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_69e75db7c5048190b8da9cd7eeedb610 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f725e4d08190b0304e45a417193b |
completed | May 2, 2026, 1:07 p.m. |
| PD | Predicate disambiguation | batch_69f49377411c8190b2188de444d76795 |
completed | May 1, 2026, 11:50 a.m. |
Created at: April 21, 2026, 2:04 p.m.