Triple
T26261663
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Middle Gorge railway station |
E656863
|
entity |
| Predicate | hasOpal |
P162097
|
FINISHED |
| Object | no |
—
|
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: no | Statement: [Middle Gorge railway station, hasOpal, no]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOpal Context triple: [Middle Gorge railway station, hasOpal, no]
-
A.
hasOpalEquivalent
Indicates that one entity corresponds to or is equivalent to another entity within the context of the Opal system or representation.
-
B.
hasOpalType
Indicates that an entity is associated with or classified by a specific type of opal.
-
C.
hasOpusForm
Indicates that an entity (such as a work or composition) is associated with a specific opus form or cataloging format.
-
D.
hasOpalLikeSmartcard
chosen
Indicates that an entity possesses or is associated with a smartcard that functions similarly to an Opal card.
-
E.
hasOpalCard
Indicates that an entity possesses or is assigned an Opal card.
- 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_69ee5b4e21bc819082be98bc9ab09796 |
completed | April 26, 2026, 6:37 p.m. |
| NER | Named-entity recognition | batch_69f676c440708190a4b9974e95d2291a |
completed | May 2, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69f675fd59608190b246383435e68fce |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 26, 2026, 9:10 p.m.