Triple
T18158153
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SHA-0 |
E434686
|
entity |
| Predicate | designDifferenceFrom |
P130695
|
FINISHED |
| Object | SHA-1 |
—
|
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: SHA-1 | Statement: [SHA-0, designDifferenceFrom, SHA-1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designDifferenceFrom Context triple: [SHA-0, designDifferenceFrom, SHA-1]
-
A.
differIn
Indicates that two entities are not the same in at least one specified aspect, attribute, or value.
-
B.
differenceDescription
Indicates a textual explanation that characterizes how two entities differ from each other.
-
C.
hasDifferentDesignsFor
Indicates that one entity provides or uses multiple distinct designs tailored for different other entities or contexts.
-
D.
designCompromiseFor
Indicates a relationship where a design is adjusted or balanced to reach a compromise that addresses the needs, constraints, or preferences of a particular entity or situation.
-
E.
adaptationDifference
Indicates a difference or change in how two entities adapt or have adapted relative to each other.
- 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_69d8b90b7a188190b3fc7b8d4a6cd20a |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4dec02d9c81909ac6203b7d59c405 |
completed | April 19, 2026, 1:55 p.m. |
| PD | Predicate disambiguation | batch_69e4331baeb88190b21f50a98c36c78e |
completed | April 19, 2026, 1:42 a.m. |
| PDg | Predicate description generation | batch_69e438f5ae2c8190b11dee46534fa5a9 |
completed | April 19, 2026, 2:07 a.m. |
Created at: April 10, 2026, 10:30 a.m.