Triple
T27818004
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Victor Comstock |
E702732
|
entity |
| Predicate | stationCallSign |
P111586
|
FINISHED |
| Object | WENN |
—
|
NE NERFINISHED |
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: WENN | Statement: [Victor Comstock, stationCallSign, WENN]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stationCallSign Context triple: [Victor Comstock, stationCallSign, WENN]
-
A.
callSignStation
chosen
Indicates that a particular call sign is assigned to or used by a specific station.
-
B.
callsign
Indicates that an entity is assigned or uses a specific radio or identification callsign as its designated identifier in communication contexts.
-
C.
callSignOwnerHeadquarters
Indicates that the headquarters of the owner associated with a given call sign is located at a specified place.
-
D.
callsignOfOperator
Indicates that one entity is the radio or communication callsign assigned to or used by another entity acting as an operator.
-
E.
callSignSpokenForm
Indicates the spoken or verbalized form used to refer to a particular call sign.
- 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_69ef840ad1e88190b5bff2d1ddec8700 |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f66c5c13808190887180099745673b |
completed | May 2, 2026, 9:27 p.m. |
| PD | Predicate disambiguation | batch_69f66abddc448190a488852f8abdeb2c |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 27, 2026, 5:46 p.m.