Triple
T9634467
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lockheed S-3 Viking |
E232892
|
entity |
| Predicate | laterPrimaryMission |
P89376
|
FINISHED |
| Object | aerial refueling |
—
|
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: aerial refueling | Statement: [Lockheed S-3 Viking, laterPrimaryMission, aerial refueling]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterPrimaryMission Context triple: [Lockheed S-3 Viking, laterPrimaryMission, aerial refueling]
-
A.
primaryMissionTo
Indicates that an entity has a main or principal mission directed toward or focused on another entity.
-
B.
intendedMission
Indicates that one entity is the planned or designated mission, task, or objective associated with another entity.
-
C.
primaryMissionProgram
Indicates that an entity serves as the main or principal program under which another entity’s mission or primary activity is organized or executed.
-
D.
secondaryMissionField
Indicates a secondary or supporting operational area or objective associated with the primary mission.
-
E.
segmentMission
Indicates that a specific mission is associated with, assigned to, or carried out within a particular segment or phase.
- 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_69ca848940cc8190b97cec654cb3bb4a |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9b2a0e2c8190ab5aaa223b1e1cde |
completed | April 1, 2026, 10:24 p.m. |
| PD | Predicate disambiguation | batch_69ccd5acfa5c8190aaba3cf548723604 |
completed | April 1, 2026, 8:22 a.m. |
| PDg | Predicate description generation | batch_69ccd93fc45c8190a823305e461e581d |
completed | April 1, 2026, 8:37 a.m. |
Created at: March 30, 2026, 8:11 p.m.