Triple
T33923361
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Egg Pictures |
E869676
|
entity |
| Predicate | creativePriority |
P199349
|
FINISHED |
| Object | strong character arcs |
—
|
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: strong character arcs | Statement: [Egg Pictures, creativePriority, strong character arcs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: creativePriority Context triple: [Egg Pictures, creativePriority, strong character arcs]
-
A.
developmentPriorityOf
Indicates the relative level of importance or urgency assigned to developing one entity compared to others.
-
B.
planningPriority
Indicates the relative importance or urgency assigned to an item, task, or objective when organizing or scheduling plans.
-
C.
prioritises
Indicates that one entity gives greater importance, preference, or precedence to another entity or task over alternatives.
-
D.
creativeScope
Indicates the range or domain within which an entity is allowed or intended to exercise creativity or generate original content.
-
E.
creativeDirectionBy
Indicates that the creative direction or overall artistic vision for something is provided or led by a specified 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_69f349992c508190aa4afa24a086cc8c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff2fbae9b48190847eefa1c227d43e |
completed | May 9, 2026, 12:59 p.m. |
| PD | Predicate disambiguation | batch_69ff2f2218048190a32224a648182b5d |
completed | May 9, 2026, 12:57 p.m. |
| PDg | Predicate description generation | batch_69ff2fb9e46c8190b36b3e0bc84f114c |
completed | May 9, 2026, 12:59 p.m. |
Created at: May 1, 2026, 1:49 a.m.