Triple
T25178646
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | City Circle tram service |
E630520
|
entity |
| Predicate | hasServiceNumber |
P2098
|
FINISHED |
| Object | 35 |
—
|
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: 35 | Statement: [City Circle tram service, hasServiceNumber, 35]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasServiceNumber Context triple: [City Circle tram service, hasServiceNumber, 35]
-
A.
serviceNumber
chosen
Indicates a unique identifying number assigned to a service, used to reference, track, or distinguish that service from others.
-
B.
serviceNumberOrEquivalent
Indicates that one entity specifies the service number or an equivalent identifying code associated with another entity.
-
C.
serviceNumbering
Indicates that a specific service is assigned or associated with a particular identifying number or code.
-
D.
serviceNumberLabel
Indicates that a label or identifier is assigned to denote the service number associated with an entity.
-
E.
serviceNumberOrRank
Indicates that one entity is identified by, or associated with, the service number or rank of 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_69e75a88fdf081908e47ae6e195c14e1 |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f67f0488bc819089fbd2d2478158d3 |
completed | May 2, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69f67e3ed894819094c067c1ef624951 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 21, 2026, 12:35 p.m.