Triple
T33279547
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Austrian Silesian railway network |
E852002
|
entity |
| Predicate | primaryNode |
P21685
|
FINISHED |
| Object | Troppau |
E241013
|
NE 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: Troppau | Statement: [Austrian Silesian railway network, primaryNode, Troppau]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryNode Context triple: [Austrian Silesian railway network, primaryNode, Troppau]
-
A.
primaryFor
Indicates that one entity serves as the main or principal option, resource, or association for another entity among possible alternatives.
-
B.
primaryComponent
chosen
Indicates that one entity serves as the main or most important component within another entity or system.
-
C.
primaryElement
Indicates that one element is the main or most important component within a set, structure, or context relative to other associated elements.
-
D.
primaryMount
Indicates that one entity serves as the main or default mount (attachment or support point) for another entity.
-
E.
primarySingle
Indicates that an entity has exactly one main or primary association of the specified type, with no additional concurrent primary associations.
- F. None of above.
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_69f349653da08190819876015a298fdb |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a35813c2b308190abf977a45aba9eaa |
completed | June 19, 2026, 5:49 p.m. |
| PD | Predicate disambiguation | batch_6a0379f338b881908e5593e45d764f4d |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:32 a.m.