Triple
T10487919
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HMY Britannia |
E247337
|
entity |
| Predicate | radioCallSign |
P1565
|
FINISHED |
| Object | GOLD |
—
|
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: GOLD | Statement: [HMY Britannia, radioCallSign, GOLD]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: radioCallSign Context triple: [HMY Britannia, radioCallSign, GOLD]
-
A.
callsign
chosen
Indicates that an entity is assigned or uses a specific radio or identification callsign as its designated identifier in communication contexts.
-
B.
callsignOfOperator
Indicates that one entity is the radio or communication callsign assigned to or used by another entity acting as an operator.
-
C.
callsignCondition
Indicates a condition or constraint that must be satisfied by an entity’s callsign within the relationship or context.
-
D.
callsignLanguage
Indicates the language in which a callsign is expressed or encoded.
-
E.
callSignSpokenForm
Indicates the spoken or verbalized form used to refer to a particular call sign.
- 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_69d381c309b88190af78aa681cf6a4c2 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d5096b609c81909e23fd8fb6426f4a |
completed | April 7, 2026, 1:40 p.m. |
| PD | Predicate disambiguation | batch_69d4fb8a30848190b33cf43f005a028e |
completed | April 7, 2026, 12:41 p.m. |
Created at: April 6, 2026, 12:23 p.m.