Triple
T3926797
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WBZ (AM) |
E93294
|
entity |
| Predicate | historicStation |
P19823
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [WBZ (AM), historicStation, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicStation Context triple: [WBZ (AM), historicStation, true]
-
A.
historicLocationType
Indicates the specific kind or category of a place based on its historical significance or role.
-
B.
historicalStructure
chosen
Indicates that the subject is a structure recognized for its historical significance or heritage value.
-
C.
historicalTerminus
Indicates that one entity serves as the historically recognized endpoint or final limit of another entity, such as a route, period, or process.
-
D.
capitalHistoric
Indicates that a location has served as a capital city at some point in history, even if it is not the current capital.
-
E.
historicManager
Indicates that an entity previously held a managerial role or position over another entity during a past period.
- 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_69aed96bfa1081908f7b30f2c647dee6 |
completed | March 9, 2026, 2:30 p.m. |
| NER | Named-entity recognition | batch_69aeed80a1e48190aa39748b9db42701 |
completed | March 9, 2026, 3:55 p.m. |
| PD | Predicate disambiguation | batch_69aee7609c4081908000ce12ae827c3f |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:23 p.m.