Triple
T8267153
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WFAN (AM) |
E193328
|
entity |
| Predicate | hasCallSignMeaning |
P15135
|
FINISHED |
| Object | “FAN” referring to sports fans |
—
|
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: “FAN” referring to sports fans | Statement: [WFAN (AM), hasCallSignMeaning, “FAN” referring to sports fans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCallSignMeaning Context triple: [WFAN (AM), hasCallSignMeaning, “FAN” referring to sports fans]
-
A.
callSignMeaning
chosen
Indicates that an entity’s call sign conveys or is associated with a particular meaning or interpretation.
-
B.
callsign
Indicates that an entity is assigned or uses a specific radio or identification callsign as its designated identifier in communication contexts.
-
C.
supportsCallSign
Indicates that one entity is capable of recognizing, handling, or operating using a specified call sign.
-
D.
hasCallsignCompanion
Indicates that one entity serves as a companion or associated partner to another entity’s callsign.
-
E.
callsignCondition
Indicates a condition or constraint that must be satisfied by an entity’s callsign within the relationship or context.
- 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_69ca82e081d48190986beaa51f498ab9 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb794e6880819084dff5df42332835 |
completed | March 31, 2026, 7:35 a.m. |
| PD | Predicate disambiguation | batch_69cb36b8707881909aca349230495a5a |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:50 p.m.