Triple
T12128960
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | No. 208 Squadron RAF |
E288882
|
entity |
| Predicate | disbandedAsFlyingUnit |
P103544
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [No. 208 Squadron RAF, disbandedAsFlyingUnit, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: disbandedAsFlyingUnit Context triple: [No. 208 Squadron RAF, disbandedAsFlyingUnit, yes]
-
A.
disbandedAsIndependentForce
Indicates that an entity ceased to exist or operate as an independent force, typically being dissolved, merged, or absorbed into another structure.
-
B.
disbandedDuring
Indicates that an entity ceased to exist or was formally dissolved at some point within the duration of a specified event or time period.
-
C.
disbandedAt
Indicates the time or date at which an organized group, body, or entity formally ceased to exist or operate.
-
D.
disbandedOrTransformed
Indicates that an entity has ceased to exist in its original form, either by being dissolved or by changing into a different organizational or structural form.
-
E.
disbandmentYear
Indicates the year in which an organization, group, or entity formally ceased to exist or was dissolved.
- 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_69d6ab4b5e4c81909950b17151eb0951 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d91841615c819097f20a7447a1b8f4 |
completed | April 10, 2026, 3:33 p.m. |
| PD | Predicate disambiguation | batch_69d91508f8008190b3a90ec0bf0953ca |
completed | April 10, 2026, 3:19 p.m. |
| PDg | Predicate description generation | batch_69d9183ec1008190b437b7d5e1f52830 |
completed | April 10, 2026, 3:33 p.m. |
Created at: April 8, 2026, 9:49 p.m.