Triple
T14418667
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canyon del Muerto |
E357521
|
entity |
| Predicate | hasTimeDepthOfOccupation |
P40474
|
FINISHED |
| Object | ancient |
—
|
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: ancient | Statement: [Canyon del Muerto, hasTimeDepthOfOccupation, ancient]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTimeDepthOfOccupation Context triple: [Canyon del Muerto, hasTimeDepthOfOccupation, ancient]
-
A.
hasTimeDepth
chosen
Indicates that something possesses or spans a measurable extent of time, such as duration, historical depth, or temporal layering.
-
B.
hasRelativeOccupation
Indicates that two people are related in such a way that one’s occupation is defined or characterized in relation to the other’s occupation.
-
C.
hasDepth
Indicates that an entity possesses a measurable extent or distance from its surface inward or from top to bottom.
-
D.
hasResidenceTime
Indicates the duration for which something remains or stays within a particular place, system, or state.
-
E.
hasAverageDepth
Indicates that an entity possesses a specified mean depth value, typically measured over its entire extent or area.
- 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_69d82793421c8190861eb0e673b085de |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de90cec8e4819087c72d82f9caacda |
completed | April 14, 2026, 7:09 p.m. |
| PD | Predicate disambiguation | batch_69de5c30467881908e770e3940295641 |
completed | April 14, 2026, 3:24 p.m. |
Created at: April 10, 2026, 1:18 a.m.