Triple
T32509996
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toby Gard |
E830904
|
entity |
| Predicate | hasCreatedFranchise |
P22111
|
FINISHED |
| Object | Tomb Raider |
—
|
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: Tomb Raider | Statement: [Toby Gard, hasCreatedFranchise, Tomb Raider]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCreatedFranchise Context triple: [Toby Gard, hasCreatedFranchise, Tomb Raider]
-
A.
createdFranchise
chosen
Indicates that one entity is the originator or founder of a franchise associated with another entity.
-
B.
createdByFranchise
Indicates that something (such as a work, product, or entity) was produced or brought into existence by a particular franchise or franchise brand.
-
C.
hadFranchise
Indicates that one entity possessed or operated a franchise right or franchise unit of another entity.
-
D.
createdForFranchise
Indicates that something was created specifically to belong to, support, or be used within a particular franchise.
-
E.
coCreatedFranchiseWith
Indicates that two or more entities jointly created or originated the same franchise.
- 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_69f3492318348190ba37fb6b5f1d67f4 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7bbf906d8819099020e548dd56bc9 |
completed | May 3, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69f7b9a2dcf88190a7c9e109e41267be |
completed | May 3, 2026, 9:09 p.m. |
Created at: May 1, 2026, 1 a.m.