Triple
T34353268
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Need for Speed Payback |
E881642
|
entity |
| Predicate | distributesOn |
P181189
|
FINISHED |
| Object | Origin |
—
|
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: Origin | Statement: [Need for Speed Payback, distributesOn, Origin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distributesOn Context triple: [Need for Speed Payback, distributesOn, Origin]
-
A.
distributesIn
Indicates that one entity allocates or hands out something (e.g., items, resources, information) within or across a specified area, group, or context.
-
B.
distributesAs
Indicates that one entity allocates or hands out something (such as resources, items, or information) to multiple other entities according to some plan or rule.
-
C.
distributionFor
Indicates a relationship where one entity serves as the distribution, delivery, or dissemination mechanism for another entity.
-
D.
distributesFrom
Indicates that something acts as the source or origin from which items, resources, or information are distributed to others.
-
E.
distributionBy
Indicates how something is allocated, arranged, or spread according to a specified criterion or grouping.
- 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_69f349bd06008190904c2f86c42749e3 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7626667f48190ad90867eb67ec582 |
completed | May 3, 2026, 2:57 p.m. |
| PD | Predicate disambiguation | batch_69f76175d6608190b60b268e20f49ed9 |
completed | May 3, 2026, 2:53 p.m. |
| PDg | Predicate description generation | batch_69f762651e088190baa21f25378a6065 |
completed | May 3, 2026, 2:57 p.m. |
Created at: May 1, 2026, 1:58 a.m.