Triple
T16998797
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SharpWriter |
E412384
|
entity |
| Predicate | advancementControl |
P126106
|
FINISHED |
| Object | manual twist control |
—
|
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: manual twist control | Statement: [SharpWriter, advancementControl, manual twist control]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: advancementControl Context triple: [SharpWriter, advancementControl, manual twist control]
-
A.
advancementStatus
Indicates the current stage or progress state of an ongoing process, project, or development.
-
B.
typeOfAdvance
Indicates that one entity represents a specific kind or category of advance (e.g., payment, progress, or development) in relation to another entity.
-
C.
advancedThrough
Indicates that an entity has progressed or moved forward within, or as a result of, a particular medium, stage, process, or pathway.
-
D.
mayAdvanceTo
Indicates that one entity is permitted or eligible to progress, move, or be promoted to another specified state, level, or position.
-
E.
endedControlOf
Indicates that one entity has ceased to exercise authority, influence, or governance over another entity or domain.
- 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_69d886cb581c8190ab05f4b429c9cd85 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d37cd6248190a7202ae754882640 |
completed | April 18, 2026, 6:54 p.m. |
| PD | Predicate disambiguation | batch_69e35d552bc08190af17ef7659e094ef |
completed | April 18, 2026, 10:30 a.m. |
| PDg | Predicate description generation | batch_69e378e037c88190935d732e0f10d5d7 |
completed | April 18, 2026, 12:28 p.m. |
Created at: April 10, 2026, 5:32 a.m.