Triple
T28105794
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shot Turquoise Marilyn |
E710357
|
entity |
| Predicate | creatorStudioLocation |
P179494
|
FINISHED |
| Object | New York City |
—
|
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 City | Statement: [Shot Turquoise Marilyn, creatorStudioLocation, New York City]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: creatorStudioLocation Context triple: [Shot Turquoise Marilyn, creatorStudioLocation, New York City]
-
A.
formerStudioOf
Indicates that a studio previously occupied or used by one entity is now associated with another entity as its former studio.
-
B.
basedAtStationStudios
Indicates that an entity (such as a program, show, or production) operates from or is primarily located at a particular station’s studios.
-
C.
developerStudioLocation
chosen
Indicates the place where a developer’s studio or primary development workspace is situated.
-
D.
foundedAsStudioIn
Indicates that an entity was originally established or created in the form of a studio at a specified time or place.
-
E.
foundedStudio
Indicates that an entity established or created a particular studio as its founder.
- 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_69ef9b71fdb081908b4a61cd7ff147c1 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f7c777e924819081a6634f549fe552 |
completed | May 3, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69f7c475c58c8190a883554231e88c88 |
completed | May 3, 2026, 9:56 p.m. |
Created at: April 27, 2026, 9:08 p.m.