Triple
T33404739
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Star Lasso Experience |
E855406
|
entity |
| Predicate | realWorldCreatorRole |
P13180
|
FINISHED |
| Object | writer-director of "Nope" |
—
|
LITERAL 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: writer-director of "Nope" | Statement: [Star Lasso Experience, realWorldCreatorRole, writer-director of "Nope"]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: realWorldCreatorRole Context triple: [Star Lasso Experience, realWorldCreatorRole, writer-director of "Nope"]
-
A.
possibleCreator
Indicates that an entity is a plausible but not definitively confirmed creator or originator of another entity.
-
B.
creatorType
chosen
Indicates the role or category of a creator in relation to the creation of something (e.g., author, artist, director).
-
C.
realWorldPerformer
Indicates that an entity serves as the actual, real-world performer of an action, role, or content represented in another entity.
-
D.
coCreator
Indicates that two or more entities jointly created or produced something together.
-
E.
créateur
Indicates that an entity is the creator or originator of another entity.
- 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_69f3496e3f1c8190bcecfa82aa9d17ff |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6f38159d08190980ad639e08f00f4 |
completed | May 3, 2026, 7:04 a.m. |
| PD | Predicate disambiguation | batch_69f6e3d7bee48190b94e0beb48a1d7fa |
completed | May 3, 2026, 5:57 a.m. |
Created at: May 1, 2026, 1:36 a.m.