Triple
T15754944
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A-4K |
E381942
|
entity |
| Predicate | successorInRNZAFRole |
P120203
|
FINISHED |
| Object | none (fast jet capability disbanded) |
—
|
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: none (fast jet capability disbanded) | Statement: [A-4K, successorInRNZAFRole, none (fast jet capability disbanded)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorInRNZAFRole Context triple: [A-4K, successorInRNZAFRole, none (fast jet capability disbanded)]
-
A.
successorInUSNTrainingRole
Indicates that one entity has taken over or followed another in a specific training role within the United States Navy.
-
B.
successorRole
Indicates that one role or position directly follows and replaces another in a sequence or organizational structure.
-
C.
successorInU.S.Service
Indicates that one entity directly follows another in holding a particular position or role within U.S. service.
-
D.
successionRole
Indicates a role or position that one entity assumes as the successor to another in a sequence of holders or office-bearers.
-
E.
successorInSomeRoles
Indicates that one entity has taken over or followed another entity in certain specified roles or positions.
- 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_69d86d9e6b44819085d1f6a969ecb74c |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e05031f6a08190bfb333eced0a59a1 |
completed | April 16, 2026, 2:57 a.m. |
| PD | Predicate disambiguation | batch_69e00531e7ac8190a4190cce4f7fab4c |
completed | April 15, 2026, 9:37 p.m. |
| PDg | Predicate description generation | batch_69e03cc871d0819085c0fc54de7984ff |
completed | April 16, 2026, 1:35 a.m. |
Created at: April 10, 2026, 4:47 a.m.