Triple
T248780
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marine One |
E5095
|
entity |
| Predicate | callSignCondition |
P7981
|
FINISHED |
| Object | used only when the President is aboard |
—
|
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: used only when the President is aboard | Statement: [Marine One, callSignCondition, used only when the President is aboard]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: callSignCondition Context triple: [Marine One, callSignCondition, used only when the President is aboard]
-
A.
callSignType
Indicates the classification or category of a call sign associated with an entity or communication.
-
B.
conditionForRecognition
chosen
Indicates that one entity specifies the requirement or circumstance under which another entity is acknowledged, accepted, or officially recognized.
-
C.
callsign
Indicates that an entity is assigned or uses a specific radio or identification callsign as its designated identifier in communication contexts.
-
D.
hasCondition
Indicates that an entity possesses, experiences, or is affected by a particular condition or state.
-
E.
callsFor
Indicates that one entity requires, demands, or requests the occurrence of another action, condition, or entity.
- 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.