Triple
T25533481
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hammer & Chisel |
E639984
|
entity |
| Predicate | pivotedFrom |
P158630
|
FINISHED |
| Object | game development |
—
|
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: game development | Statement: [Hammer & Chisel, pivotedFrom, game development]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pivotedFrom Context triple: [Hammer & Chisel, pivotedFrom, game development]
-
A.
laterPivotedTo
Indicates that an entity changed direction, focus, or strategy at a subsequent time toward another specified activity, role, or domain.
-
B.
promotedFrom
Indicates that an entity has advanced to a new position, role, or status from a specified prior one.
-
C.
orientedFrom
Indicates that one entity has a defined direction or orientation starting at or determined by another reference entity.
-
D.
relocatedOrFolded
Indicates that an entity has either moved its operations to a new location or ceased operating by merging, closing, or otherwise folding.
-
E.
riftedFrom
Indicates that one entity has split, separated, or broken away from another, creating a division or gap between them.
- 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_69e75dbf3f9c8190b3f2a75d1b75d127 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f8652c908190bee57d3f2663e6b2 |
completed | May 2, 2026, 1:13 p.m. |
| PD | Predicate disambiguation | batch_69f468421ba08190880eac99135e5970 |
completed | May 1, 2026, 8:45 a.m. |
| PDg | Predicate description generation | batch_69f46d361c348190b5fdfd805ecde01b |
completed | May 1, 2026, 9:07 a.m. |
Created at: April 21, 2026, 3:16 p.m.