Triple
T37782611
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zach Adams |
E941869
|
entity |
| Predicate | worksWithEngine |
P179173
|
FINISHED |
| Object | custom game engine for Dwarf Fortress |
—
|
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: custom game engine for Dwarf Fortress | Statement: [Zach Adams, worksWithEngine, custom game engine for Dwarf Fortress]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: worksWithEngine Context triple: [Zach Adams, worksWithEngine, custom game engine for Dwarf Fortress]
-
A.
worksFor
Indicates that one entity is employed by or performs work on behalf of another entity, typically an organization or individual.
-
B.
engineeringWork
chosen
Indicates a relationship where an entity performs, produces, or is involved in an engineering-related task, project, or output.
-
C.
worksWith
Indicates that two entities collaborate or perform tasks together in a shared work-related context.
-
D.
associatedWithEngine
Indicates a relationship in which something is connected, linked, or related to an engine, typically through use, function, or dependency.
-
E.
worksTo
Indicates that one entity performs work or exerts effort in order to achieve, support, or contribute to another entity or outcome.
- 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_69f76ee5cb0c81909a363d1c929156c0 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fd231cab588190ad0953dc8f4af8f2 |
completed | May 7, 2026, 11:41 p.m. |
| PD | Predicate disambiguation | batch_69fd1aa3f1c481909fe6e9cab1383551 |
completed | May 7, 2026, 11:05 p.m. |
Created at: May 3, 2026, 4:19 p.m.