Triple
T21651896
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CQU |
E534357
|
entity |
| Predicate | partOfIdentifierScheme |
P1285
|
FINISHED |
| Object | Sydney Trains station codes |
—
|
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: Sydney Trains station codes | Statement: [CQU, partOfIdentifierScheme, Sydney Trains station codes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partOfIdentifierScheme Context triple: [CQU, partOfIdentifierScheme, Sydney Trains station codes]
-
A.
designationScheme
Indicates the classification or naming system under which an entity’s designations or identifiers are defined.
-
B.
hasIdentifierSystem
chosen
Indicates that an entity is associated with a particular system or scheme used to assign and manage its identifiers.
-
C.
identifierFor
Indicates that one entity serves as a unique identifying label or code for another entity.
-
D.
isPartOfStandardizationSystem
Indicates that something belongs to, or is included within, a defined standardization framework, scheme, or system.
-
E.
identificationScope
Indicates the contextual boundary or extent within which an entity is uniquely identified or recognized.
- 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_69e0c466aec88190ba39c7543dbc8ba2 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef591594a08190bf0ddd0a0c0922ba |
completed | April 27, 2026, 12:39 p.m. |
| PD | Predicate disambiguation | batch_69e696826c3c81909270791e79760937 |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:36 p.m.