Triple
T31824679
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TeamTO |
E812357
|
entity |
| Predicate | worksInFormat |
P38824
|
FINISHED |
| Object | computer-generated imagery |
—
|
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: computer-generated imagery | Statement: [TeamTO, worksInFormat, computer-generated imagery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: worksInFormat Context triple: [TeamTO, worksInFormat, computer-generated imagery]
-
A.
operatesInFormat
chosen
Indicates that an entity functions, performs its role, or is carried out using a specified format.
-
B.
hasWorkingFormat
Indicates that one entity possesses or is associated with a functional or operational format of another entity.
-
C.
basedInWorkFormat
Indicates that an entity operates or is situated within a particular work format (such as remote, hybrid, or on-site) as its primary mode of working.
-
D.
presentedInFormat
Indicates that something is expressed, delivered, or made available using a particular format or representation.
-
E.
worksFor
Indicates that one entity is employed by or performs work on behalf of another entity, typically an organization or individual.
- 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_69f348e97fa48190aa06286962af6dee |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f7675b12848190a3569cfda29c5b0e |
completed | May 3, 2026, 3:18 p.m. |
| PD | Predicate disambiguation | batch_69f762f4b59481909f70074f11825bfb |
completed | May 3, 2026, 3 p.m. |
Created at: April 30, 2026, 11:46 p.m.