Triple
T23333256
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northrop N-156 project |
E591502
|
entity |
| Predicate | ledToVariant |
P117575
|
FINISHED |
| Object | single-seat fighter variant |
—
|
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: single-seat fighter variant | Statement: [Northrop N-156 project, ledToVariant, single-seat fighter variant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ledToVariant Context triple: [Northrop N-156 project, ledToVariant, single-seat fighter variant]
-
A.
exportVariantOf
Indicates that one entity is an exported version or externally released form derived from another, original entity.
-
B.
mobileVariant
Indicates that one entity is a mobile-specific version or adaptation of another entity.
-
C.
laterColorVariant
Indicates that one entity is a color variant that appeared or was introduced after the other entity in time.
-
D.
governsVariant
Indicates a regulatory relationship where one entity controls, influences, or determines the behavior or state of a specific variant of another entity.
-
E.
resultedInVehicleVariant
chosen
Indicates that one event, process, or action led to the creation or emergence of a specific variant of a vehicle.
- 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_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. |
Created at: April 17, 2026, 5:16 p.m.