Triple
T14686893
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ingleburn railway station |
E344929
|
entity |
| Predicate | hasAccessiblePath |
P114063
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Ingleburn railway station, hasAccessiblePath, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAccessiblePath Context triple: [Ingleburn railway station, hasAccessiblePath, yes]
-
A.
hasPathAccess
Indicates that one entity is permitted to traverse or use a specified path or route associated with another entity.
-
B.
isAccessible
Indicates that one entity can be reached, used, or entered by another entity without obstruction or restriction.
-
C.
hasAccessibleConnection
chosen
Indicates that there exists a way for one entity to reach or interact with another in a manner that meets defined accessibility requirements.
-
D.
areAccessibleAt
Indicates that certain entities can be reached, used, or entered at a specified location, time, or context.
-
E.
hasAccessRouteTo
Indicates that one entity possesses a path, connection, or means of reaching or interacting with 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_69d822e34b348190ada4d1cdb6c7c226 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb58306548190b981956a83a84b95 |
completed | April 14, 2026, 9:45 p.m. |
| PD | Predicate disambiguation | batch_69de6579fb7881909becc8f5822b39d4 |
completed | April 14, 2026, 4:04 p.m. |
Created at: April 10, 2026, 1:28 a.m.