Triple
T25972907
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FINNCOMM |
E645854
|
entity |
| Predicate | historicalSuccessorOperator |
P88961
|
FINISHED |
| Object | Nordic Regional Airlines |
—
|
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: Nordic Regional Airlines | Statement: [FINNCOMM, historicalSuccessorOperator, Nordic Regional Airlines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalSuccessorOperator Context triple: [FINNCOMM, historicalSuccessorOperator, Nordic Regional Airlines]
-
A.
historicalSuccessorState
Indicates that one state historically followed and replaced another state in time as its successor.
-
B.
successorOperator
Indicates that one operator directly follows another in a defined sequence or ordering.
-
C.
historicalSuccessorInNationStateContext
Indicates that one political entity directly follows another as its successor within the historical continuity of a nation-state.
-
D.
introducedAsSuccessorOf
chosen
Indicates that one entity was formally presented or designated to take over the role, position, or function previously held by another entity.
-
E.
predecessorOperator
Indicates that one operator precedes another in an ordered sequence or process.
- 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_69e77e8768648190b27bb578f14bcb88 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f7308a096081909d66a56f3c926806 |
completed | May 3, 2026, 11:24 a.m. |
| PD | Predicate disambiguation | batch_69f72a00c5f081908b6539d15baf4e12 |
completed | May 3, 2026, 10:57 a.m. |
Created at: April 22, 2026, 8:51 a.m.