Triple
T30675791
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ebony Maw |
E780903
|
entity |
| Predicate | CGIStudio |
P170006
|
FINISHED |
| Object | Industrial Light & Magic |
—
|
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: Industrial Light & Magic | Statement: [Ebony Maw, CGIStudio, Industrial Light & Magic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: CGIStudio Context triple: [Ebony Maw, CGIStudio, Industrial Light & Magic]
-
A.
animationStudio
Indicates that one entity is an animation studio responsible for creating, producing, or animating the other entity.
-
B.
animationSoftware
Indicates that an entity is a software application used to create, edit, or render animations for another entity (such as a project, asset, or user).
-
C.
characterDesigner
Indicates a relationship where an entity is responsible for designing or creating the visual or conceptual characteristics of a character.
-
D.
gpuDesigner
Indicates that one entity is the designer or creator of a particular GPU associated with another entity.
-
E.
illustratorOf
Indicates that one entity serves as the illustrator or creator of the visual artwork for another entity, such as a book, article, or other work.
- 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_69f224a7fc208190a07d6d3879b31640 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68b18c42881909cc1ae94fd13e0a1 |
completed | May 2, 2026, 11:39 p.m. |
| PD | Predicate disambiguation | batch_69f6861170d08190bb98be609d436f84 |
completed | May 2, 2026, 11:17 p.m. |
| PDg | Predicate description generation | batch_69f688034580819086a0f9100645f8ba |
completed | May 2, 2026, 11:25 p.m. |
Created at: April 29, 2026, 8:32 p.m.