Triple
T38116514
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stephansplatz station |
E951804
|
entity |
| Predicate | isMajorNodeInNetwork |
P40323
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Stephansplatz station, isMajorNodeInNetwork, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMajorNodeInNetwork Context triple: [Stephansplatz station, isMajorNodeInNetwork, true]
-
A.
isMajorNodeOf
Indicates that one node serves as a primary or central node within, or in relation to, another structure, network, or system.
-
B.
isMajorRouteInSystem
Indicates that a route functions as a primary or significant corridor within a specified transportation or network system.
-
C.
majorNode
chosen
Indicates that an entity functions as a primary or most important node within a larger structure or network.
-
D.
isMajorFor
Indicates that one entity serves as the primary field of academic specialization (major) for another entity, typically a student.
-
E.
isMajorPoolAt
Indicates that a particular location or site serves as a primary or significant pool (e.g., of resources, data, or participants) for the referenced 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_69f76f07734c8190814e937e12257a78 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fe9fb9735c8190a360b556c9d00b3f |
completed | May 9, 2026, 2:45 a.m. |
| PD | Predicate disambiguation | batch_69fe9eaa88008190a9b2a469dc685002 |
completed | May 9, 2026, 2:40 a.m. |
Created at: May 3, 2026, 4:21 p.m.