Triple
T31356921
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CAC Mustang |
E799760
|
entity |
| Predicate | successorInRAAFService |
P198599
|
FINISHED |
| Object | CAC Sabre |
—
|
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: CAC Sabre | Statement: [CAC Mustang, successorInRAAFService, CAC Sabre]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorInRAAFService Context triple: [CAC Mustang, successorInRAAFService, CAC Sabre]
-
A.
successorInU.S.Service
Indicates that one entity directly follows another in holding a particular position or role within U.S. service.
-
B.
successorInRNZAFRole
Indicates that one entity took over and continued the same role or position in the RNZAF that was previously held by another entity.
-
C.
successorInUSNTrainingRole
Indicates that one entity has taken over or followed another in a specific training role within the United States Navy.
-
D.
enteredUSAFServiceAs
Indicates that an individual began active service in the United States Air Force in a specified role, rank, or capacity.
-
E.
successorInRAFService
Indicates that one entity took over or continued the role, position, or service of another within the Royal Air Force (RAF).
- 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_69f224e5e9bc8190a16339328897c4f8 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fef5cf8da881908260ec633830375d |
completed | May 9, 2026, 8:52 a.m. |
| PD | Predicate disambiguation | batch_69fef455e40481909861c82007b79bc0 |
completed | May 9, 2026, 8:46 a.m. |
| PDg | Predicate description generation | batch_69fef5cec8208190b85665ab6a511a08 |
completed | May 9, 2026, 8:52 a.m. |
Created at: April 29, 2026, 9:17 p.m.