Triple
T24994499
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cranbourne–Pakenham corridor |
E625530
|
entity |
| Predicate | servedByProject |
P29878
|
FINISHED |
| Object | Metro Tunnel (via Sunbury–Dandenong corridor integration) |
—
|
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: Metro Tunnel (via Sunbury–Dandenong corridor integration) | Statement: [Cranbourne–Pakenham corridor, servedByProject, Metro Tunnel (via Sunbury–Dandenong corridor integration)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servedByProject Context triple: [Cranbourne–Pakenham corridor, servedByProject, Metro Tunnel (via Sunbury–Dandenong corridor integration)]
-
A.
servedByService
Indicates that something is provided, handled, or fulfilled by a particular service.
-
B.
byProject
Indicates that something is organized, grouped, or associated according to a specific project.
-
C.
servedByServiceVia
Indicates that something receives service or is fulfilled through a specific service acting as the intermediary or delivery mechanism.
-
D.
backedProject
Indicates that one entity has provided support or resources, typically financial, to help initiate or sustain another entity’s project.
-
E.
fedByProject
chosen
Indicates that something receives its necessary input, resources, or data as a result of the execution or output of a specific project.
- 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_69f6430a93a48190854ce71df680b2fa |
completed | May 2, 2026, 6:31 p.m. |
| PD | Predicate disambiguation | batch_69f641da05b881909f6283c988639c53 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 18, 2026, 6:04 a.m.