Triple
T5162070
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | No. 207 Squadron RAF |
E116457
|
entity |
| Predicate | formedAsRAFUnit |
P41696
|
FINISHED |
| Object | 1 April 1918 |
—
|
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 April 1918 | Statement: [No. 207 Squadron RAF, formedAsRAFUnit, 1 April 1918]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formedAsRAFUnit Context triple: [No. 207 Squadron RAF, formedAsRAFUnit, 1 April 1918]
-
A.
formedUnit
chosen
Indicates that one entity has been organized or constituted into a specific unit or group, establishing a formal unit-level relationship between them.
-
B.
formerSubunit
Indicates that one entity was previously a subunit or subordinate part of another entity, but no longer holds that status.
-
C.
subunitOf
Indicates that one entity functions as a component or smaller part within the structure or organization of another, larger entity.
-
D.
commissionedUnit
Indicates that one entity formally authorizes or assigns another entity (the commissioned unit) to carry out a specific task, role, or function.
-
E.
associatedUnitType
Indicates that one entity is linked to or characterized by a particular type or category of unit.
- 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_69bd445edb3881909b93b34d260717fc |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd79268ea48190a22d3350babc153c |
completed | March 20, 2026, 4:43 p.m. |
| PD | Predicate disambiguation | batch_69bd77b36c008190b91011a9fa52b3d2 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:44 p.m.