Triple
T7258955
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | No. 92 Squadron RAF |
E159596
|
entity |
| Predicate | reformedOn |
P75984
|
FINISHED |
| Object | 1939-10-10 |
—
|
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: 1939-10-10 | Statement: [No. 92 Squadron RAF, reformedOn, 1939-10-10]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reformedOn Context triple: [No. 92 Squadron RAF, reformedOn, 1939-10-10]
-
A.
laterReformedAs
Indicates that an entity was subsequently reorganized, renamed, or transformed into another entity at a later time.
-
B.
reformedOffice
Indicates that an office or official position has been reorganized, restructured, or fundamentally changed from its previous form.
-
C.
underwentReformation
Indicates that an entity experienced a significant process of change, restructuring, or reform that altered its previous state or practices.
-
D.
reformedBody
Indicates that an entity has undergone a process of structural or organizational change resulting in a newly formed or reorganized body.
-
E.
functionAfterReformation
Indicates that one function or role exists or is performed in the state or period following a process of reformation or reform.
- 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_69c68838f9948190875fd60b2351230c |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6eb088dac8190b353f6ea3d686025 |
completed | March 27, 2026, 8:39 p.m. |
| PD | Predicate disambiguation | batch_69c6e76876608190ac4652bc7153302e |
completed | March 27, 2026, 8:24 p.m. |
| PDg | Predicate description generation | batch_69c6eb06acd881908a1735fbbbd5756f |
completed | March 27, 2026, 8:39 p.m. |
Created at: March 27, 2026, 2:57 p.m.