Triple
T23953549
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sydney Harbour Tunnel Company |
E603115
|
entity |
| Predicate | tunnelLinks |
P149928
|
FINISHED |
| Object | Sydney central business district |
—
|
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: Sydney central business district | Statement: [Sydney Harbour Tunnel Company, tunnelLinks, Sydney central business district]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tunnelLinks Context triple: [Sydney Harbour Tunnel Company, tunnelLinks, Sydney central business district]
-
A.
tunnels
Indicates that one entity passes through, under, or within another entity via a tunnel-like passage or structure.
-
B.
tunnelsStatus
Indicates the current operational or physical condition of tunnels, such as whether they are open, closed, or otherwise restricted.
-
C.
numberOfTunnels
Indicates the quantity of tunnels associated with or passing through a given entity or location.
-
D.
tunnelType
Indicates the specific kind or classification of a tunnel associated with an entity.
-
E.
tunnelAssociation
chosen
Indicates a relationship where one entity is connected to, passes through, or is linked via a tunnel-like structure or pathway to 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_69e2953e4924819093f1c24c03476b42 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f1d0d558748190a51b5732a3e6713c |
completed | April 29, 2026, 9:35 a.m. |
| PD | Predicate disambiguation | batch_69f1615518088190a206f54e2fdb14a3 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 9:21 p.m.