Triple
T15866722
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Danish Army Air Corps |
E384731
|
entity |
| Predicate | dissolvedAsIndependentBranch |
P120823
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Danish Army Air Corps, dissolvedAsIndependentBranch, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dissolvedAsIndependentBranch Context triple: [Danish Army Air Corps, dissolvedAsIndependentBranch, true]
-
A.
dissolvedAsAgency
Indicates that an organization ceased to exist or operate in its capacity as an agency.
-
B.
dissolvedByMerger
Indicates that an entity ceased to exist as an independent entity because it was legally combined into another entity through a merger.
-
C.
endedByDissolution
Indicates that a relationship, agreement, or entity was terminated specifically through a formal dissolution process.
-
D.
wasDissolvedAfter
Indicates that one entity ceased to exist or operate at a later point in time than another entity’s dissolution.
-
E.
isIndependentBranchOf
Indicates that one branch or subdivision operates autonomously and is not subordinate to the other branch or organization it is associated with.
- 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_69d86da4e86481909f1325fdc971b5ec |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e174de2cd48190ab18e48c9f051a2a |
completed | April 16, 2026, 11:46 p.m. |
| PD | Predicate disambiguation | batch_69e142b976c081908d3ba3e705419f3a |
completed | April 16, 2026, 8:12 p.m. |
| PDg | Predicate description generation | batch_69e174da2c2c819099ec46616798245a |
completed | April 16, 2026, 11:46 p.m. |
Created at: April 10, 2026, 4:50 a.m.