Triple
T111978
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Naval Air Service |
E2266
|
entity |
| Predicate | dateOfRoyalAirForceFormation |
P7130
|
FINISHED |
| Object | 1918-04-01 |
—
|
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: 1918-04-01 | Statement: [Royal Naval Air Service, dateOfRoyalAirForceFormation, 1918-04-01]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateOfRoyalAirForceFormation Context triple: [Royal Naval Air Service, dateOfRoyalAirForceFormation, 1918-04-01]
-
A.
commanderOfRAF
Indicates that one entity serves as the commander or head of the Royal Air Force in relation to another entity.
-
B.
dateOfUnionFormation
Indicates the date on which a union was formally established or came into existence.
-
C.
foundedOn
Indicates that an entity was established, created, or brought into existence on a specific date or point in time.
-
D.
foundedAt
Indicates the time or date at which an entity (such as an organization, project, or institution) was established or created.
-
E.
primaryBritishFighterAircraft
Indicates that an aircraft serves as the main or most important fighter aircraft used by British military forces.
- 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_69a24fcdaeb48190a2d796677e4b3281 |
completed | Feb. 28, 2026, 2:15 a.m. |
| NER | Named-entity recognition | batch_69a258808ff08190a06b6206f635612b |
completed | Feb. 28, 2026, 2:52 a.m. |
| PD | Predicate disambiguation | batch_69a256425a488190959d71e39e699d90 |
completed | Feb. 28, 2026, 2:43 a.m. |
| PDg | Predicate description generation | batch_69a2587e598c81909e1082b813971f48 |
completed | Feb. 28, 2026, 2:52 a.m. |
Created at: Feb. 28, 2026, 2:20 a.m.