Triple
T31122158
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Specification O.8/38 |
E793250
|
entity |
| Predicate | aircraftConfigurationRequired |
P3541
|
FINISHED |
| Object | two-seat fighter |
—
|
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: two-seat fighter | Statement: [Specification O.8/38, aircraftConfigurationRequired, two-seat fighter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aircraftConfigurationRequired Context triple: [Specification O.8/38, aircraftConfigurationRequired, two-seat fighter]
-
A.
aircraftConfiguration
chosen
Indicates the specific arrangement or setup of an aircraft’s components, systems, or features for a given purpose or operating condition.
-
B.
aircraftConfigurationProduced
Indicates that a specific aircraft configuration has been manufactured or produced.
-
C.
intendedAircraft
Indicates that an aircraft is the one planned or designated to be used for a particular flight, mission, or operation.
-
D.
aircraftRoleRequired
Indicates that a specific operational role or function is required of an aircraft within a given context or mission.
-
E.
supportsAircraft
Indicates that one entity is capable of accommodating, carrying, or enabling the operation of an aircraft.
- 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_69f224d0a7688190af3fe3e6e26d01ed |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6df450014819099d118e5c2d697fa |
completed | May 3, 2026, 5:38 a.m. |
| PD | Predicate disambiguation | batch_69f6de07836481908785cde9c511920b |
completed | May 3, 2026, 5:32 a.m. |
Created at: April 29, 2026, 9:04 p.m.