Triple
T26747104
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LKAB Malmtrafik |
E674429
|
entity |
| Predicate | operatesOnRelation |
P194458
|
FINISHED |
| Object | Sweden–Norway rail corridor |
—
|
NE NERFINISHED |
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: Sweden–Norway rail corridor | Statement: [LKAB Malmtrafik, operatesOnRelation, Sweden–Norway rail corridor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatesOnRelation Context triple: [LKAB Malmtrafik, operatesOnRelation, Sweden–Norway rail corridor]
-
A.
operatesOnPropertyOf
Indicates that an action or process is applied specifically to a property or attribute of an entity, rather than to the entity itself.
-
B.
operatesOnProperty
Indicates that one entity performs an action or has an effect specifically targeting a particular property or attribute of another entity.
-
C.
definesOperationOn
Indicates that one entity specifies or establishes the operation that is applied to another entity.
-
D.
relatesOperator
Indicates that one entity is associated with, or functions as, an operator in relation to another entity.
-
E.
typeOfRelationsHandled
Indicates the kinds or categories of relationships that an entity is responsible for managing or processing.
- 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_69eecda63a3881908095c47900692e65 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69fd76d1e5208190a6f26651492d1e3c |
completed | May 8, 2026, 5:38 a.m. |
| PD | Predicate disambiguation | batch_69fd702a226c81908edfda00f4be4130 |
completed | May 8, 2026, 5:10 a.m. |
| PDg | Predicate description generation | batch_69fd76d0d7608190b350336d6c18182d |
completed | May 8, 2026, 5:38 a.m. |
Created at: April 27, 2026, 3:52 a.m.