Triple
T34095036
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Morphoses/The Wheeldon Company |
E874401
|
entity |
| Predicate | creativeModel |
P162899
|
FINISHED |
| Object | project-based company |
—
|
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: project-based company | Statement: [Morphoses/The Wheeldon Company, creativeModel, project-based company]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: creativeModel Context triple: [Morphoses/The Wheeldon Company, creativeModel, project-based company]
-
A.
creativeOutput
Indicates that an entity produces, originates, or is responsible for a creative work or result.
-
B.
hasCreativeModel
chosen
Indicates that an entity is associated with or utilizes a particular creative model (e.g., a generative or design model) for producing creative outputs.
-
C.
creationType
Indicates the manner or process by which something was brought into existence or produced.
-
D.
crea
Indicates that one entity creates, produces, or brings into existence another entity.
-
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_69f349a735208190a1dbfb1c2a121059 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff3b32ee148190a3ba3b7600943fef |
completed | May 9, 2026, 1:48 p.m. |
| PD | Predicate disambiguation | batch_69ff3a238af88190a2c2245e30299e48 |
completed | May 9, 2026, 1:44 p.m. |
Created at: May 1, 2026, 1:52 a.m.