Triple
T33931028
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 144th Armored Signal Company |
E869889
|
entity |
| Predicate | communicationsMedium |
P2798
|
FINISHED |
| Object | radio |
—
|
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: radio | Statement: [144th Armored Signal Company, communicationsMedium, radio]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: communicationsMedium Context triple: [144th Armored Signal Company, communicationsMedium, radio]
-
A.
mediumOfCommunicationFor
Indicates that one entity serves as the medium or channel through which another entity communicates or conveys information.
-
B.
commonMedium
Indicates that two or more entities share the same medium or channel through which interaction, communication, or transmission occurs.
-
C.
applicationMedium
Indicates the medium or channel through which an application is submitted or communicated (e.g., online, paper, email).
-
D.
informationMedium
Indicates the medium or channel through which information is conveyed or communicated between entities.
-
E.
communicationChannel
chosen
Indicates a medium or method through which information is transmitted between parties.
- 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_69f3499a59788190bff762a891471b31 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f71fb1ab3881908e2f7c0e6f23db49 |
completed | May 3, 2026, 10:13 a.m. |
| PD | Predicate disambiguation | batch_69f71cc6397881909aaad37a9daa8a7e |
completed | May 3, 2026, 10 a.m. |
Created at: May 1, 2026, 1:49 a.m.