Triple
T36246952
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Herning Fremad |
E891688
|
entity |
| Predicate | mergerPartnerIn |
P6600
|
FINISHED |
| Object | FC Midtjylland |
E256172
|
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: FC Midtjylland | Statement: [Herning Fremad, mergerPartnerIn, FC Midtjylland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mergerPartnerIn Context triple: [Herning Fremad, mergerPartnerIn, FC Midtjylland]
-
A.
mergerPartner
chosen
Indicates that two entities are involved as counterparties in a merger transaction with each other.
-
B.
acquisitionPartner
Indicates a relationship where one entity collaborates with or assists another in acquiring a third entity, asset, or resource.
-
C.
mergerType
Indicates the specific kind or category of merger relationship that exists between the involved entities.
-
D.
cooperationPartner
Indicates that two entities are engaged in a collaborative relationship, working together toward shared goals or mutual benefit.
-
E.
selectedPartner
Indicates that one entity has been chosen or designated as the partner of another entity.
- 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_69f76e44993481908fa75e4c48d0aab3 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7ba6d06f48190a71b5a2f19e2232f |
completed | May 3, 2026, 9:13 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a396e04a33c81908288beb268abf51e |
completed | June 22, 2026, 5:16 p.m. |
| PD | Predicate disambiguation | batch_69f7b9a4aad48190a62e41c5e39339d9 |
completed | May 3, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:09 p.m.