Triple
T8556190
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Volvo RM12 |
E202568
|
entity |
| Predicate | intendedAircraftGeneration |
P17727
|
FINISHED |
| Object | fourth-generation 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: fourth-generation fighter | Statement: [Volvo RM12, intendedAircraftGeneration, fourth-generation fighter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendedAircraftGeneration Context triple: [Volvo RM12, intendedAircraftGeneration, fourth-generation fighter]
-
A.
aircraftGeneration
chosen
Indicates a generational relationship between aircraft, such as one model being a successor, predecessor, or belonging to a specific generation relative to another.
-
B.
intendedAircraft
Indicates that an aircraft is the one planned or designated to be used for a particular flight, mission, or operation.
-
C.
aircraftConfigurationProduced
Indicates that a specific aircraft configuration has been manufactured or produced.
-
D.
aircraftType
Indicates the specific model or category of aircraft associated with an entity or event.
-
E.
hasBasedAircraft
Indicates that an aircraft is regularly stationed or primarily based at a particular location or facility.
- 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_69ca832610e08190b3b6c6cd2c250255 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe88bcce081909e12e4037a0e6323 |
completed | March 31, 2026, 3:30 p.m. |
| PD | Predicate disambiguation | batch_69cbd1160fcc8190aa380a73610af731 |
completed | March 31, 2026, 1:50 p.m. |
Created at: March 30, 2026, 6:19 p.m.