Triple
T12151291
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | No. 541 Squadron RAF |
E289459
|
entity |
| Predicate | finalDisbandmentDate |
P62226
|
FINISHED |
| Object | 1 September 1957 |
—
|
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: 1 September 1957 | Statement: [No. 541 Squadron RAF, finalDisbandmentDate, 1 September 1957]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalDisbandmentDate Context triple: [No. 541 Squadron RAF, finalDisbandmentDate, 1 September 1957]
-
A.
disbandedAt
chosen
Indicates the time or date at which an organized group, body, or entity formally ceased to exist or operate.
-
B.
disbandmentYear
Indicates the year in which an organization, group, or entity formally ceased to exist or was dissolved.
-
C.
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.
-
D.
disbandsAfter
Indicates that one entity ceases to exist or formally dissolves at some point following the occurrence or completion of another entity or event.
-
E.
wasDissolvedAfter
Indicates that one entity ceased to exist or operate at a later point in time than another entity’s dissolution.
- 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_69d6ab4c6710819097a9d228382dde43 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d915d7109481908bf5fe512bba3c89 |
completed | April 10, 2026, 3:23 p.m. |
| PD | Predicate disambiguation | batch_69d9150c18148190bf8152189c0e5fca |
completed | April 10, 2026, 3:19 p.m. |
Created at: April 8, 2026, 9:49 p.m.