Triple
T11220475
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chicxulub Pueblo |
E265546
|
entity |
| Predicate | hasNearbyScientificSite |
P52075
|
FINISHED |
| Object | Chicxulub crater drilling locations |
—
|
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: Chicxulub crater drilling locations | Statement: [Chicxulub Pueblo, hasNearbyScientificSite, Chicxulub crater drilling locations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyScientificSite Context triple: [Chicxulub Pueblo, hasNearbyScientificSite, Chicxulub crater drilling locations]
-
A.
hasNearbyArchaeologicalSite
Indicates that an entity is located close to or in the vicinity of an archaeological site.
-
B.
hasNearbyObservatories
Indicates that one entity has one or more observatories located in close geographic proximity to it.
-
C.
nearGeologicalSite
chosen
Indicates that one entity is located in close physical proximity to a geological site or feature.
-
D.
hasNearbyPilgrimageSite
Indicates that one entity is located close to a place used as a pilgrimage site for religious or spiritual journeys.
-
E.
nearestResearchStation
Indicates that one research station is the closest in distance to a given location or entity compared to all other research stations.
- 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_69d6aac59460819089b9848b27f57848 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e8eb84c48190b4f3bede254afde2 |
completed | April 9, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69d75cfbbb188190861efd5d94fe27da |
completed | April 9, 2026, 8:02 a.m. |
Created at: April 8, 2026, 9:30 p.m.