Triple
T248789
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marine One |
E5095
|
entity |
| Predicate | secondaryMission |
P2114
|
FINISHED |
| Object | transport of senior White House staff |
—
|
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: transport of senior White House staff | Statement: [Marine One, secondaryMission, transport of senior White House staff]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondaryMission Context triple: [Marine One, secondaryMission, transport of senior White House staff]
-
A.
secondaryGoal
Indicates that something serves as a subordinate or supporting objective in addition to a primary goal.
-
B.
secondaryFunction
chosen
Indicates that an entity has an additional, supporting role or purpose beyond its primary function.
-
C.
secondaryPosition
Indicates that an entity holds an additional, non-primary role, location, or status alongside its main one.
-
D.
mission
Indicates that an entity is assigned or engaged in a specific task, operation, or purpose-directed undertaking.
-
E.
secondaryArmament
Indicates that one entity serves as a secondary or auxiliary weapon system associated with another primary platform or armament.
- 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_69a257c4bf688190a46ebbf411ab7473 |
completed | Feb. 28, 2026, 2:49 a.m. |
| NER | Named-entity recognition | batch_69a25d35aa288190966b6e15af1525cb |
completed | Feb. 28, 2026, 3:12 a.m. |
| PD | Predicate disambiguation | batch_69a25b64ea3081908de626a0e1445bdb |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 2:54 a.m.