Triple
T32030943
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WOR (AM) |
E817954
|
entity |
| Predicate | movedCityOfLicenseTo |
P173498
|
FINISHED |
| Object | New York, New York |
—
|
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: New York, New York | Statement: [WOR (AM), movedCityOfLicenseTo, New York, New York]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: movedCityOfLicenseTo Context triple: [WOR (AM), movedCityOfLicenseTo, New York, New York]
-
A.
formerCityOfLicense
Indicates that an entity previously held, but no longer holds, the official city of license designation for another entity (typically a broadcast station).
-
B.
cityOfLicense
Indicates the city in which an entity (typically a broadcast station or similar regulated service) is officially licensed or authorized to operate.
-
C.
movedHeadquartersToCity
Indicates that an organization has relocated its main headquarters to a specified city.
-
D.
movedOn
Indicates that an entity changed its position or location from one place to another at some point in time.
-
E.
movedPremises
Indicates that an entity has changed its location or base of operations from one set of premises to another.
- 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_69f348fbc8148190b3c0f95d4772b153 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b56ed31481908c3e5d749e46bad9 |
completed | May 3, 2026, 2:39 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a7bdb481908d16a32f49e38c2c |
completed | May 3, 2026, 2:32 a.m. |
| PDg | Predicate description generation | batch_69f6b49339048190b617a6749f648825 |
completed | May 3, 2026, 2:36 a.m. |
Created at: May 1, 2026, 12:18 a.m.