Triple
T32547577
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rome Metro Line B |
E831885
|
entity |
| Predicate | hasBranchOpening |
P181272
|
FINISHED |
| Object | Rome Metro Line B1 opened 2012 |
—
|
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: Rome Metro Line B1 opened 2012 | Statement: [Rome Metro Line B, hasBranchOpening, Rome Metro Line B1 opened 2012]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBranchOpening Context triple: [Rome Metro Line B, hasBranchOpening, Rome Metro Line B1 opened 2012]
-
A.
hasBranchOffice
Indicates that one organization maintains a branch office or subsidiary location in another place or entity.
-
B.
openedAirportBranch
Indicates that an entity established and began operating a branch or location at an airport.
-
C.
hasOpening
Indicates that one entity possesses or features an opening, gap, or entrance that allows access, passage, or exposure.
-
D.
mayHaveBranchOfficesIn
Indicates that an entity is permitted or allowed to establish branch offices in a specified location.
-
E.
hasFederallyRecognizedBranch
Indicates that an entity possesses at least one branch, division, or subsidiary that is officially recognized by a federal authority.
- F. None of above. chosen
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_69f34925fd08819084cfe4ec566cb704 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7675b12848190a3569cfda29c5b0e |
completed | May 3, 2026, 3:18 p.m. |
| PD | Predicate disambiguation | batch_69f762f4b59481909f70074f11825bfb |
completed | May 3, 2026, 3 p.m. |
| PDg | Predicate description generation | batch_69f76759b3c48190ad8f1b33596f98c4 |
completed | May 3, 2026, 3:18 p.m. |
Created at: May 1, 2026, 1:02 a.m.