Triple
T28862695
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EcoJet |
E728905
|
entity |
| Predicate | cityOfMainBase |
P55226
|
FINISHED |
| Object | Santa Cruz de la Sierra |
—
|
NE NERFINISHED |
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: Santa Cruz de la Sierra | Statement: [EcoJet, cityOfMainBase, Santa Cruz de la Sierra]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cityOfMainBase Context triple: [EcoJet, cityOfMainBase, Santa Cruz de la Sierra]
-
A.
formerBaseCity
Indicates that a location previously served as the primary base or home city for an entity, but no longer holds that status.
-
B.
mainTownOn
Indicates that one town is the primary or principal town located on or associated with a particular geographic feature, route, or area.
-
C.
cityOfMajorPresence
Indicates that an entity has a significant or primary operational, demographic, or functional presence in the specified city.
-
D.
homeCityOf
Indicates that a particular city is the primary place of residence or origin for a given person or organization.
-
E.
hasMainPlace
chosen
Indicates that one entity is designated as the primary or central location associated with another entity.
- 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_69f031a01cbc8190ba87270bb6fe4639 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f6691f5e188190b12c7b2eb729a45e |
completed | May 2, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69f6659b62fc8190b21555d0ba54db2d |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 6:47 a.m.