Triple
T10383579
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tlachihualtepetl Pyramid |
E244702
|
entity |
| Predicate | hasTunnelLength |
P12895
|
FINISHED |
| Object | several kilometers of excavated tunnels |
—
|
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 kilometers of excavated tunnels | Statement: [Tlachihualtepetl Pyramid, hasTunnelLength, several kilometers of excavated tunnels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTunnelLength Context triple: [Tlachihualtepetl Pyramid, hasTunnelLength, several kilometers of excavated tunnels]
-
A.
hasTunnelLengthApprox
chosen
Indicates that an entity has a tunnel whose length is approximately a specified value.
-
B.
hasTunnel
Indicates that one entity possesses, contains, or is connected by a tunnel to another entity.
-
C.
hasTunnelShape
Indicates that something possesses a form or configuration resembling a tunnel, typically elongated, enclosed, and passage-like.
-
D.
tunnelCircumference
Indicates the circular distance around the inner boundary of a tunnel’s cross-section.
-
E.
tunnelDiameterCharacteristic
Indicates the specified diameter-related property or measurement associated with a tunnel.
- 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_69d381b5116081908d85227bab6d3c0c |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4e9a2aafc8190aa11d14852fa1599 |
completed | April 7, 2026, 11:25 a.m. |
| PD | Predicate disambiguation | batch_69d4dfb0e7a88190bec0b7a52c70dfe2 |
completed | April 7, 2026, 10:42 a.m. |
Created at: April 6, 2026, 12:04 p.m.