Triple
T32715453
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CCR Ponte |
E836509
|
entity |
| Predicate | operatedSafetyServices |
P5884
|
FINISHED |
| Object | Rio–Niterói Bridge |
—
|
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: Rio–Niterói Bridge | Statement: [CCR Ponte, operatedSafetyServices, Rio–Niterói Bridge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatedSafetyServices Context triple: [CCR Ponte, operatedSafetyServices, Rio–Niterói Bridge]
-
A.
safetyOfLifeServiceOperational
Indicates that a safety-of-life service is currently active and functioning as intended.
-
B.
operatesService
chosen
Indicates that an agent runs, manages, or provides a particular service.
-
C.
operatedPassengerServices
Indicates that an entity provided and managed transportation services specifically for carrying passengers.
-
D.
operatesServiceTo
Indicates that one entity runs or provides a transportation or service route to another entity or location.
-
E.
operationalService
Indicates that one entity provides, performs, or is responsible for carrying out a particular service or operation for 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_69f34935455881909088975d79460418 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a00262d71488190a769783fb09e5803 |
completed | May 10, 2026, 6:31 a.m. |
| PD | Predicate disambiguation | batch_6a0023985f148190a335a3fb93e9981e |
completed | May 10, 2026, 6:20 a.m. |
Created at: May 1, 2026, 1:11 a.m.