Triple
T36095568
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Behemoth |
E1044047
|
entity |
| Predicate | designStudio |
P96064
|
FINISHED |
| Object | Legacy Effects |
—
|
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: Legacy Effects | Statement: [Behemoth, designStudio, Legacy Effects]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designStudio Context triple: [Behemoth, designStudio, Legacy Effects]
-
A.
designBureau
Indicates that an entity functions as a design bureau responsible for planning, developing, or engineering designs for another entity or project.
-
B.
hasDesignStudio
chosen
Indicates that an entity owns, operates, or is associated with a design studio.
-
C.
projectionDesignBy
Indicates that a projection or projected visual element is created or designed by a particular agent or designer.
-
D.
designUse
Indicates that one entity is used as a design basis, purpose, or intended functional use for another entity.
-
E.
designCollaboration
Indicates a collaborative relationship in which two or more entities jointly participate in the design process or co-create a design outcome.
- 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_69f76e32d60c8190ba781ffaaab4aa3d |
completed | May 3, 2026, 3:48 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. |
Created at: May 3, 2026, 4:08 p.m.