Triple
T470122
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WEEI-FM |
E8536
|
entity |
| Predicate | callSignMeaning |
P15135
|
FINISHED |
| Object | WEEI = originally from earlier Boston station WEEI (AM) |
—
|
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: WEEI = originally from earlier Boston station WEEI (AM) | Statement: [WEEI-FM, callSignMeaning, WEEI = originally from earlier Boston station WEEI (AM)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: callSignMeaning Context triple: [WEEI-FM, callSignMeaning, WEEI = originally from earlier Boston station WEEI (AM)]
-
A.
callSignType
Indicates the classification or category of a call sign associated with an entity or communication.
-
B.
callsign
Indicates that an entity is assigned or uses a specific radio or identification callsign as its designated identifier in communication contexts.
-
C.
inscriptionMeaning
Indicates that an inscription conveys a particular meaning, message, or content.
-
D.
titleMeaning
Indicates that one entity expresses or explains the meaning, significance, or interpretation of another entity’s title.
-
E.
formerCallSign
Indicates that one identifier was previously used as the call sign for the other entity before being changed or replaced.
- F. None of above. chosen
Provenance (4 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_69a2e7f3aeb48190a19453e3a043f486 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2efef8b788190857ebf66df562d59 |
completed | Feb. 28, 2026, 1:38 p.m. |
| PD | Predicate disambiguation | batch_69a2edebb3988190907992a584b4e260 |
completed | Feb. 28, 2026, 1:30 p.m. |
| PDg | Predicate description generation | batch_69a2ef257a548190a96bfa0cf6183976 |
completed | Feb. 28, 2026, 1:35 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.