Triple
T30854865
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Teleférico de Zacatecas |
E785890
|
entity |
| Predicate | operatesAbove |
P3695
|
FINISHED |
| Object | streets of Zacatecas historic center |
—
|
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: streets of Zacatecas historic center | Statement: [Teleférico de Zacatecas, operatesAbove, streets of Zacatecas historic center]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatesAbove Context triple: [Teleférico de Zacatecas, operatesAbove, streets of Zacatecas historic center]
-
A.
operatesOver
chosen
Indicates that one entity performs actions or exerts functional control across, upon, or throughout another entity or domain.
-
B.
operatesAtHigh
Indicates that an entity functions or performs its activity at a high level, intensity, capacity, or setting relative to a defined scale or standard.
-
C.
operatesBelow
Indicates that one entity functions, acts, or is positioned at a lower level, layer, or hierarchy relative to another entity.
-
D.
operatesBy
Indicates that an entity performs its function, action, or process through the use or application of another entity (e.g., a method, mechanism, or principle).
-
E.
operateIn
Indicates that an entity performs its activities, functions, or services within a specified location, context, or domain.
- 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_69f224b91c14819084e764832fe67a57 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69ff795d25d08190b7584c72be39d309 |
completed | May 9, 2026, 6:13 p.m. |
| PD | Predicate disambiguation | batch_69ff78a90fbc8190a62c57456dc1d4ad |
completed | May 9, 2026, 6:10 p.m. |
Created at: April 29, 2026, 8:46 p.m.