Triple
T32069296
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rust-eze Racing |
E818966
|
entity |
| Predicate | franchiseDistributor |
P173800
|
FINISHED |
| Object | Walt Disney Pictures |
—
|
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: Walt Disney Pictures | Statement: [Rust-eze Racing, franchiseDistributor, Walt Disney Pictures]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: franchiseDistributor Context triple: [Rust-eze Racing, franchiseDistributor, Walt Disney Pictures]
-
A.
distributesFranchise
Indicates that one party grants or allocates franchise rights or opportunities to another party.
-
B.
franchiseDistributorContext
Indicates the contextual relationship in which a distributor operates under a franchise arrangement, specifying how distribution activities are governed by that franchise.
-
C.
franchiseSoldTo
Indicates that the rights to operate or own a franchise have been transferred from one party to another.
-
D.
franchisingAuthority
Indicates that one entity has the legal or contractual authority to grant, manage, or oversee franchise rights to another entity.
-
E.
franchiseOf
Indicates that one entity operates as a franchise belonging to or licensed by another entity.
- 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_69f348fecc088190af1470afe5a969f0 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6ba1733408190af579d93a7946508 |
completed | May 3, 2026, 2:59 a.m. |
| PD | Predicate disambiguation | batch_69f6b6293188819080d5041ca0adb969 |
completed | May 3, 2026, 2:42 a.m. |
| PDg | Predicate description generation | batch_69f6b960ca4081909a77690c2b122f5e |
completed | May 3, 2026, 2:56 a.m. |
Created at: May 1, 2026, 12:23 a.m.