Triple
T22108208
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | P-82 Twin Mustang |
E546343
|
entity |
| Predicate | designationChange |
P60795
|
FINISHED |
| Object | redesignated F-82 in 1948 |
—
|
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: redesignated F-82 in 1948 | Statement: [P-82 Twin Mustang, designationChange, redesignated F-82 in 1948]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designationChange Context triple: [P-82 Twin Mustang, designationChange, redesignated F-82 in 1948]
-
A.
designationEffect
Indicates the effect, consequence, or outcome that results from assigning or designating something a particular status, role, or label.
-
B.
designationBegan
Indicates the point in time when a particular designation, title, or status for an entity first became effective.
-
C.
officialNameChangeTo
chosen
Indicates that an entity’s official name has been changed from a previous name to a new specified name.
-
D.
changedUnder
Indicates that one entity has undergone alteration, modification, or transformation as a result of the influence, action, or conditions imposed by another entity.
-
E.
changedNameIn
Indicates that an entity has altered or adopted a different name within a specific context, time period, or jurisdiction.
- 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_69e11e378dc08190896d6a51597afd5a |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f1291adc74819092c7753bb6f3768d |
completed | April 28, 2026, 9:39 p.m. |
| PD | Predicate disambiguation | batch_69e71b2ed7348190b6fa2e52f54393fb |
completed | April 21, 2026, 6:37 a.m. |
Created at: April 16, 2026, 8:30 p.m.