Triple
T17201980
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Flying Corps station |
E417496
|
entity |
| Predicate | supportedEquipment |
P126386
|
FINISHED |
| Object | military aircraft |
—
|
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: military aircraft | Statement: [Royal Flying Corps station, supportedEquipment, military aircraft]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportedEquipment Context triple: [Royal Flying Corps station, supportedEquipment, military aircraft]
-
A.
supportedIn
Indicates that one entity is valid, applicable, or functionally enabled within the context, environment, platform, or scope defined by another entity.
-
B.
supportedPlatform
Indicates that one entity (such as a system, application, or service) is compatible with and can operate on a particular platform.
-
C.
supportedAs
Indicates that one entity is accepted, recognized, or treated as being in the role, type, or representation of another entity.
-
D.
supportedSystem
Indicates that one entity provides compatibility, functionality, or operational support for another system.
-
E.
previouslySupportedHardware
Indicates that the subject hardware was supported in the past but is no longer currently supported.
- 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_69d886d6ba8c819093215917b3d01689 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42db014b08190b88a5001e9f7811b |
completed | April 19, 2026, 1:19 a.m. |
| PD | Predicate disambiguation | batch_69e3831e354881908c5505ffd15c84e9 |
completed | April 18, 2026, 1:11 p.m. |
| PDg | Predicate description generation | batch_69e3873f62108190966c4e741ebd548d |
completed | April 18, 2026, 1:29 p.m. |
Created at: April 10, 2026, 5:38 a.m.