Triple
T29416871
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ScummVM |
E746048
|
entity |
| Predicate | nonGoal |
P167155
|
FINISHED |
| Object | does not include game data files |
—
|
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: does not include game data files | Statement: [ScummVM, nonGoal, does not include game data files]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nonGoal Context triple: [ScummVM, nonGoal, does not include game data files]
-
A.
notAbout
Indicates that a given entity, statement, or resource does not concern, reference, or pertain to another specified entity or topic.
-
B.
goalIn
Indicates that one entity’s objective, aim, or intended outcome is located within, directed toward, or achieved inside another entity or context.
-
C.
nonScholastic
Indicates that an activity, event, or attribute is related to areas outside formal academic or scholarly pursuits.
-
D.
secondaryGoal
Indicates that something serves as a subordinate or supporting objective in addition to a primary goal.
-
E.
nonConstructive
Indicates that the relationship or action does not provide a direct, explicit method or example to realize or build the object, outcome, or proof it asserts exists.
- 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_69f0a79f6d5c8190a350baed0157e06f |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f66a666e5c8190ae53ea01f2195ac1 |
completed | May 2, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69f66339175c819080bd70f0ff7057b1 |
completed | May 2, 2026, 8:48 p.m. |
| PDg | Predicate description generation | batch_69f663ff176c8190aaadb475f75daee4 |
completed | May 2, 2026, 8:52 p.m. |
Created at: April 28, 2026, 3:02 p.m.