Triple
T34179997
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Need for Speed: World |
E876785
|
entity |
| Predicate | hasServerShutdown |
P200757
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Need for Speed: World, hasServerShutdown, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasServerShutdown Context triple: [Need for Speed: World, hasServerShutdown, true]
-
A.
hasServer
Indicates that one entity functions as or possesses a server that provides services or resources to another entity.
-
B.
designedToAllowShutdownOf
Indicates that one entity is specifically created or configured to enable the shutdown or power-off of another entity.
-
C.
usShutdownCompleted
Indicates that a shutdown process in the United States context has been fully completed.
-
D.
hasServerComponent
Indicates that an entity includes, depends on, or is associated with a particular server-side component.
-
E.
hasFunctionAfterDecommissioning
Indicates that an entity continues to perform a specific function or role after it has been formally decommissioned.
- 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_69f349ae640c8190b9cd220b5368d8b6 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ffab5adf2c819084700c5ea34615bf |
completed | May 9, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69ffaabffa208190b5214ca17cc8a5ea |
completed | May 9, 2026, 9:44 p.m. |
| PDg | Predicate description generation | batch_69ffab59fe408190b72f13016de9953c |
completed | May 9, 2026, 9:47 p.m. |
Created at: May 1, 2026, 1:54 a.m.