Triple
T7252746
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wooden Wonder |
E157643
|
entity |
| Predicate | appliesToAircraftRole |
P57567
|
FINISHED |
| Object | fighter-bomber |
—
|
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: fighter-bomber | Statement: [Wooden Wonder, appliesToAircraftRole, fighter-bomber]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliesToAircraftRole Context triple: [Wooden Wonder, appliesToAircraftRole, fighter-bomber]
-
A.
usedOnAircraftRole
chosen
Indicates that something is employed or applied in the context of a specific role or function on an aircraft.
-
B.
aircraftRoleSupported
Indicates that a given role or function is supported or enabled for a particular aircraft.
-
C.
testAircraftRole
Indicates that an aircraft is assigned or evaluated for a specific operational role or function.
-
D.
aircraftRoleRequired
Indicates that a specific operational role or function is required of an aircraft within a given context or mission.
-
E.
referredAircraftRole
Indicates that one aircraft is mentioned or designated in relation to another aircraft’s role, function, or status within a specific context or event.
- 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_69c6882d81d4819085f7ff862951ee4f |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6ea9d41908190bb76c6a5b9d5b1a2 |
completed | March 27, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69c6e7666ffc81908bf643d8257e6337 |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 2:56 p.m.