Triple
T34922664
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stray Dolls |
E1007188
|
entity |
| Predicate | creativeVisionBy |
P50489
|
FINISHED |
| Object | Sonejuhi Sinha |
—
|
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: Sonejuhi Sinha | Statement: [Stray Dolls, creativeVisionBy, Sonejuhi Sinha]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: creativeVisionBy Context triple: [Stray Dolls, creativeVisionBy, Sonejuhi Sinha]
-
A.
creativeScope
Indicates the range or domain within which an entity is allowed or intended to exercise creativity or generate original content.
-
B.
basedOnCreativeVisionOf
chosen
Indicates that something is created, designed, or developed according to the artistic or conceptual vision conceived by a particular entity.
-
C.
creativeDirectionBy
Indicates that the creative direction or overall artistic vision for something is provided or led by a specified entity.
-
D.
creativeOutput
Indicates that an entity produces, originates, or is responsible for a creative work or result.
-
E.
creativeUniverse
Indicates a relationship where an entity is responsible for originating, shaping, or imaginatively generating a universe or complete world.
- 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_69f76dc2b6b0819095a61debbd405269 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ff6074bcd4819090b72cd6209ff206 |
completed | May 9, 2026, 4:27 p.m. |
| PD | Predicate disambiguation | batch_69ff600aba888190812a6e7eca0283b8 |
completed | May 9, 2026, 4:25 p.m. |
Created at: May 3, 2026, 4 p.m.