Triple
T13812372
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AF-KL |
E331924
|
entity |
| Predicate | hasMergerOrigin |
P3654
|
FINISHED |
| Object | merger of Air France and KLM |
—
|
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: merger of Air France and KLM | Statement: [AF-KL, hasMergerOrigin, merger of Air France and KLM]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMergerOrigin Context triple: [AF-KL, hasMergerOrigin, merger of Air France and KLM]
-
A.
hasMerger
Indicates a relationship where two or more entities combine into a single entity through a merger event.
-
B.
hasOwnerBeforeMerger
Indicates that an entity had a particular owner prior to a merger event taking place.
-
C.
laterMergedWith
Indicates that one entity was combined into and became part of another entity at a subsequent point in time.
-
D.
hasOriginIn
chosen
Indicates that something begins, arises, or is derived from a specified source, place, or cause.
-
E.
hasOriginFeature
Indicates that an entity possesses a specific characteristic, attribute, or feature related to its origin or source.
- 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_69d81c59f8808190a851bc56afdc55e9 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de027198f8819095da3e714ac241f5 |
completed | April 14, 2026, 9:01 a.m. |
| PD | Predicate disambiguation | batch_69dbc862e9608190bd8a3d883959b7e4 |
completed | April 12, 2026, 4:29 p.m. |
Created at: April 9, 2026, 10:12 p.m.