Triple
T10193086
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Princes Bridge |
E238086
|
entity |
| Predicate | tramRoutes |
P92625
|
FINISHED |
| Object | multiple Melbourne tram routes |
—
|
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: multiple Melbourne tram routes | Statement: [Princes Bridge, tramRoutes, multiple Melbourne tram routes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tramRoutes Context triple: [Princes Bridge, tramRoutes, multiple Melbourne tram routes]
-
A.
tramOperator
Indicates that one entity operates, manages, or runs tram services for another entity or area.
-
B.
rapidTransitSystem
Indicates a transportation relationship where people or goods are moved via a high-capacity, high-frequency public transit system designed for rapid travel over urban or regional routes.
-
C.
railServicesTo
Indicates that rail transportation services operate from one location to another specified destination.
-
D.
tradRoutes
Indicates a relationship where one location serves as a trade route to or from another location, facilitating the movement of goods or commerce between them.
-
E.
subwayLine
Indicates that there is a subway line connection or service relationship between the referenced entities.
- 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_69ca84de1b208190bf17bb305b002605 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdedc675008190b8248325f5a208bf |
completed | April 2, 2026, 4:17 a.m. |
| PD | Predicate disambiguation | batch_69cd7c8477648190bc55c56aeec507d3 |
completed | April 1, 2026, 8:13 p.m. |
| PDg | Predicate description generation | batch_69cd7edc6cf081909d95859d880a4059 |
completed | April 1, 2026, 8:23 p.m. |
Created at: March 30, 2026, 9:13 p.m.