Triple
T27289604
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lockheed XP-49 |
E688580
|
entity |
| Predicate | laterEngine |
P59116
|
FINISHED |
| Object | Allison V-1710 |
—
|
NE NERFINISHED |
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: Allison V-1710 | Statement: [Lockheed XP-49, laterEngine, Allison V-1710]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterEngine Context triple: [Lockheed XP-49, laterEngine, Allison V-1710]
-
A.
laterEngineer
Indicates that one entity becomes an engineer at a later time than another entity.
-
B.
successorEngine
Indicates that one engine directly follows and replaces another in a sequence or version lineage.
-
C.
laterBase
Indicates that one event, state, or version occurs or is valid at a later time than another referenced event, state, or version.
-
D.
laterPropulsion
chosen
Indicates that one propulsion system, method, or event occurs after another in time.
-
E.
developedEngine
Indicates that one entity created, designed, or engineered an engine for another entity or purpose.
- 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_69ef355998e08190bdff849e8f33adce |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69fbbc49da8c8190902bbb05d2477cab |
completed | May 6, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69fbb13f34b08190bbbb220ac1e6e666 |
completed | May 6, 2026, 9:23 p.m. |
Created at: April 27, 2026, 11:14 a.m.