Triple
T5722673
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SHAMROCK |
E126183
|
entity |
| Predicate | radioTelephonyDesignatorType |
P4790
|
FINISHED |
| Object | ICAO radio callsign |
—
|
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: ICAO radio callsign | Statement: [SHAMROCK, radioTelephonyDesignatorType, ICAO radio callsign]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: radioTelephonyDesignatorType Context triple: [SHAMROCK, radioTelephonyDesignatorType, ICAO radio callsign]
-
A.
telephoneStandard
Indicates that there is a relationship involving the use of a particular telephone standard or protocol for communication between entities.
-
B.
callingCodeType
Indicates the type or category of a telephone calling code associated with an entity.
-
C.
callSignType
chosen
Indicates the classification or category of a call sign associated with an entity or communication.
-
D.
telephoneNumberingPlan
Indicates a relationship where a telephone numbering plan defines or governs how telephone numbers are structured, assigned, or managed for a given telecommunication context.
-
E.
callingCode
Indicates the telephone country or area code associated with an entity for making phone calls.
- 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_69c0082f723881908ce8bb13a0c0f8b7 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c029014588819094a2a0f6f9b66bab |
completed | March 22, 2026, 5:38 p.m. |
| PD | Predicate disambiguation | batch_69c021c47f4c81909e6849c3be3e951c |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:46 p.m.