Triple
T23991104
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hurdman station |
E605068
|
entity |
| Predicate | openedForConfederationLine |
P154533
|
FINISHED |
| Object | 2019 |
—
|
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: 2019 | Statement: [Hurdman station, openedForConfederationLine, 2019]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openedForConfederationLine Context triple: [Hurdman station, openedForConfederationLine, 2019]
-
A.
formedConfederation
Indicates that two or more entities joined together to create a confederation, establishing a formal union or alliance among them.
-
B.
enteredConfederation
Indicates that an entity became a member of, or formally joined, a confederation.
-
C.
confederation1
Indicates a relationship where multiple entities join together in a loose alliance or union while retaining their individual autonomy.
-
D.
formerConfederation
Indicates that an entity was previously part of a confederation but is no longer a member.
-
E.
confederationFoundedBy
Indicates that a confederation was established or created by a specific person, group, or entity.
- F. None of above. chosen
Provenance (4 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_69e295463f7c8190b1c19dbd114641b9 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f1d38b37648190afb003cded3a7484 |
completed | April 29, 2026, 9:46 a.m. |
| PD | Predicate disambiguation | batch_69f1615994c48190a5de95d3f7e5cd0a |
completed | April 29, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f16e348b548190b76e50f9b611f76d |
completed | April 29, 2026, 2:34 a.m. |
Created at: April 17, 2026, 9:37 p.m.