Triple
T24994849
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yarra Trams |
E625539
|
entity |
| Predicate | operatesIconicService |
P5884
|
FINISHED |
| Object | City Circle Tram |
—
|
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: City Circle Tram | Statement: [Yarra Trams, operatesIconicService, City Circle Tram]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatesIconicService Context triple: [Yarra Trams, operatesIconicService, City Circle Tram]
-
A.
operatesService
chosen
Indicates that an agent runs, manages, or provides a particular service.
-
B.
operatesServiceTo
Indicates that one entity runs or provides a transportation or service route to another entity or location.
-
C.
operateIn
Indicates that an entity performs its activities, functions, or services within a specified location, context, or domain.
-
D.
operationalService
Indicates that one entity provides, performs, or is responsible for carrying out a particular service or operation for another entity.
-
E.
ledToOperationalServiceOf
Indicates that one entity caused or enabled another entity to enter or begin operational service.
- 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_69e2ff2611c081908710457fbe6d376b |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f68f670b608190a0b6ab60d722b4e0 |
completed | May 2, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69f68b78f29481908cc8f390496dee97 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 18, 2026, 6:04 a.m.