Triple
T23333249
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northrop N-156 project |
E591502
|
entity |
| Predicate | aircraftRoleTargeted |
P151900
|
FINISHED |
| Object | 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: fighter | Statement: [Northrop N-156 project, aircraftRoleTargeted, fighter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aircraftRoleTargeted Context triple: [Northrop N-156 project, aircraftRoleTargeted, fighter]
-
A.
targetedAircraft
Indicates that one entity has selected or designated an aircraft as the object of an attack, tracking, or other directed action.
-
B.
carriedAircraftRole
Indicates the functional role or mission type that an aircraft serves when it is carried by another platform (such as a ship or larger aircraft).
-
C.
aircraftRoleSpecialization
Indicates that one aircraft role is a more specific, specialized form of another, more general aircraft role.
-
D.
notableAircraftRole
Indicates that an aircraft is notably associated with performing a particular role or function.
-
E.
basedAircraftRole
Indicates that an aircraft is regularly stationed at a particular location in a specified operational role or function.
- 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_69e25d20156c81908c5c53195bd9c738 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f197eecc5c81908089eb43bc701196 |
completed | April 29, 2026, 5:32 a.m. |
| PD | Predicate disambiguation | batch_69effcf8ca2c8190887d4f4656617d21 |
completed | April 28, 2026, 12:19 a.m. |
| PDg | Predicate description generation | batch_69f01d88b4ec8190a2a17a88e0eda178 |
completed | April 28, 2026, 2:38 a.m. |
Created at: April 17, 2026, 5:16 p.m.