Triple
T25415173
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yankee Station |
E636809
|
entity |
| Predicate | callSignOrigin |
P134994
|
FINISHED |
| Object | NATO phonetic alphabet word "Yankee" |
—
|
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: NATO phonetic alphabet word "Yankee" | Statement: [Yankee Station, callSignOrigin, NATO phonetic alphabet word "Yankee"]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: callSignOrigin Context triple: [Yankee Station, callSignOrigin, NATO phonetic alphabet word "Yankee"]
-
A.
callSignDerivedFrom
Indicates that one entity’s call sign is derived or formed from another entity, such as its name, identifier, or related designation.
-
B.
hasCallSignOrigin
chosen
Indicates that an entity’s call sign originates from, or is derived based on, a particular source, place, or context.
-
C.
callSignNumber
Indicates the specific identifying number assigned as a call sign to an entity for communication or identification purposes.
-
D.
callSignStation
Indicates that a particular call sign is assigned to or used by a specific station.
-
E.
callSignScope
Indicates that a particular call sign is valid, applicable, or in effect only within a specified scope, context, or jurisdiction.
- 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_69e75db4135881909acc287ebcb7a505 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5b0119ee0819088c4985bd7862cab |
completed | May 2, 2026, 8:04 a.m. |
| PD | Predicate disambiguation | batch_69f45d0dbc8c8190beecce679fce90a4 |
completed | May 1, 2026, 7:58 a.m. |
Created at: April 21, 2026, 1:55 p.m.