Triple
T22882639
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pinwheel |
E567515
|
entity |
| Predicate | locatedInBroadcastArea |
P46665
|
FINISHED |
| Object | Columbus, Ohio (initially) |
—
|
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: Columbus, Ohio (initially) | Statement: [Pinwheel, locatedInBroadcastArea, Columbus, Ohio (initially)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInBroadcastArea Context triple: [Pinwheel, locatedInBroadcastArea, Columbus, Ohio (initially)]
-
A.
locationOfBroadcast
chosen
Indicates the place or geographic area from which a broadcast is transmitted or originates.
-
B.
isInArea
Indicates that one entity is located within the spatial bounds or region defined by another entity.
-
C.
locatedInTransportArea
Indicates that an entity is situated within a designated transport-related area or zone.
-
D.
hasAreaOfCoverage
Indicates that an entity provides services, influence, or applicability within a specified geographic or conceptual region.
-
E.
isLocatedInAdministrativeArea
Indicates that one entity is situated within the geographic or jurisdictional boundaries of a specified administrative area (such as a city, county, state, or region).
- 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_69e2458a92ec81908fc1cd5f6407d2ab |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17f5cd98c8190b3c31ffd4c066331 |
completed | April 29, 2026, 3:47 a.m. |
| PD | Predicate disambiguation | batch_69ef3b6b2e2481908258156937b5a745 |
completed | April 27, 2026, 10:33 a.m. |
Created at: April 17, 2026, 3:39 p.m.