Triple
T2342725
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chicxulub impact crater |
E45060
|
entity |
| Predicate | burialDepth |
P35790
|
FINISHED |
| Object | several hundred meters below surface in many areas |
—
|
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: several hundred meters below surface in many areas | Statement: [Chicxulub impact crater, burialDepth, several hundred meters below surface in many areas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: burialDepth Context triple: [Chicxulub impact crater, burialDepth, several hundred meters below surface in many areas]
-
A.
buriedUnder
chosen
Indicates that one entity is located beneath another entity in such a way that it is covered or concealed by it, as if buried.
-
B.
burialBy
Indicates that one entity is responsible for burying or interring another entity.
-
C.
burialCoordinates
Indicates the geographic location where an entity is buried, typically expressed as spatial coordinates.
-
D.
buriedWith
Indicates that one entity is interred in the same grave, tomb, or burial site as another entity.
-
E.
dateOfBurial
Indicates the specific date on which an entity was buried.
- 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_69a88917935081909b755dbf38e81024 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abcade3c808190ab3803538ccbe620 |
completed | March 7, 2026, 6:51 a.m. |
| PD | Predicate disambiguation | batch_69abc59616a8819099711834e6f1ccd6 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:52 p.m.