Triple
T28105795
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shot Turquoise Marilyn |
E710357
|
entity |
| Predicate | creatorStudioName |
P186361
|
FINISHED |
| Object | The Factory |
—
|
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: The Factory | Statement: [Shot Turquoise Marilyn, creatorStudioName, The Factory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: creatorStudioName Context triple: [Shot Turquoise Marilyn, creatorStudioName, The Factory]
-
A.
formerStudioOf
Indicates that a studio previously occupied or used by one entity is now associated with another entity as its former studio.
-
B.
createdByStudioFounder
Indicates that something (such as a work, project, or company) was created by the person who founded the studio.
-
C.
creatorType
Indicates the role or category of a creator in relation to the creation of something (e.g., author, artist, director).
-
D.
creatorNameInOriginalScript
Indicates that the relationship specifies the name of the creator written in the original script or writing system used by that creator.
-
E.
créateur
Indicates that an entity is the creator or originator of another entity.
- 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_69ef9b71fdb081908b4a61cd7ff147c1 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f7cec454a88190a9f3bbee2b856636 |
completed | May 3, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69f7c8977c288190997a892ec5f756ed |
completed | May 3, 2026, 10:13 p.m. |
| PDg | Predicate description generation | batch_69f7cec398ac819081c954a993c323ee |
completed | May 3, 2026, 10:40 p.m. |
Created at: April 27, 2026, 9:08 p.m.