Triple
T33414324
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hollywood Squares |
E855670
|
entity |
| Predicate | notableCenterSquare |
P206457
|
FINISHED |
| Object | Paul Lynde |
E542338
|
NE 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: Paul Lynde | Statement: [Hollywood Squares, notableCenterSquare, Paul Lynde]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableCenterSquare Context triple: [Hollywood Squares, notableCenterSquare, Paul Lynde]
-
A.
notableCenter
Indicates that an entity is recognized as an important or prominent central point, hub, or focal location for another entity or activity.
-
B.
notableCityCenter
Indicates that a location serves as a prominent or significant central area within a city.
-
C.
notableLocationOn
Indicates that a particular location is especially significant or noteworthy in relation to a specified entity or context.
-
D.
isSocialCenterOf
Indicates that one entity serves as the primary gathering place or hub for social activities and interactions for another entity or group.
-
E.
notableCorner
Indicates that a specific corner or intersection is distinguished or significant in some notable way within a given context.
- F. None of above. chosen
Provenance (5 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_69f3496f04a08190804e56ac5098b8e4 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a36f9a821d481908ffd5b01b0597793 |
completed | June 20, 2026, 8:35 p.m. |
| PD | Predicate disambiguation | batch_6a0379f505c88190ac0879ab422c3054 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c7fb9f88190b384b1b68200aef0 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 1, 2026, 1:36 a.m.