Triple
T38132059
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Single Ticket |
E952249
|
entity |
| Predicate | operatorCityAuthority |
P60825
|
FINISHED |
| Object | São Paulo municipal government |
E1594227
|
NE 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: São Paulo municipal government | Statement: [Single Ticket, operatorCityAuthority, São Paulo municipal government]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatorCityAuthority Context triple: [Single Ticket, operatorCityAuthority, São Paulo municipal government]
-
A.
cityAuthority
Indicates that an entity holds official governing or administrative authority over a city.
-
B.
servesAsMunicipalAuthorityFor
Indicates that an entity functions as the official municipal governing or administrative authority for a specified locality or jurisdiction.
-
C.
cityGovernment
Indicates that a city’s governing authority has jurisdiction, control, or administrative responsibility over the referenced entity.
-
D.
operatorCity
chosen
Indicates the city in which an operator is based or primarily operates.
-
E.
statePlanningAuthority
Indicates that an entity functions as, or is associated with, a governmental body responsible for land-use planning and development control at the state level.
- F. None of above.
Provenance (4 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_69f76f083548819082bd2bbf53c79e8e |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a03460f3a8c8190ae3f4cd69e0e54d9 |
completed | May 12, 2026, 3:23 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a416827eb20819093ae2e1f26893989 |
completed | June 28, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_6a0345810b3481908aec06ab2b712e12 |
completed | May 12, 2026, 3:21 p.m. |
Created at: May 3, 2026, 4:21 p.m.