Triple
T1530652
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marine Two |
E32432
|
entity |
| Predicate | communicationDomain |
P2798
|
FINISHED |
| Object | aviation radio communications |
—
|
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: aviation radio communications | Statement: [Marine Two, communicationDomain, aviation radio communications]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: communicationDomain Context triple: [Marine Two, communicationDomain, aviation radio communications]
-
A.
communicationChannel
chosen
Indicates a medium or method through which information is transmitted between parties.
-
B.
communicationMode
Indicates the method or channel through which communication between entities is carried out.
-
C.
enablesCommunicationWith
Indicates that one entity provides the means or capability for another entity to communicate with a specified party or system.
-
D.
enablesCommunicationBetween
Indicates that one entity provides the means or capability for communication to occur between two or more other entities.
-
E.
communicationStatus
Indicates the current state or condition of a communication process or exchange between entities (e.g., pending, active, failed, completed).
- 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_69a885ea86308190998f6bc14bb91f8e |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a933ddc5a881909cdf503f2bc29bd4 |
completed | March 5, 2026, 7:42 a.m. |
| PD | Predicate disambiguation | batch_69a907ae8f688190ad9000ea1e018585 |
completed | March 5, 2026, 4:33 a.m. |
Created at: March 4, 2026, 7:26 p.m.