Triple
T37927412
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GIR |
E946128
|
entity |
| Predicate | differenceFromSIRUnit |
P58687
|
FINISHED |
| Object | constructed from random junk |
—
|
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: constructed from random junk | Statement: [GIR, differenceFromSIRUnit, constructed from random junk]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: differenceFromSIRUnit Context triple: [GIR, differenceFromSIRUnit, constructed from random junk]
-
A.
differenceFromIFF
Indicates that two entities differ from each other if and only if a specified condition or set of criteria holds.
-
B.
differenceFromStates
Indicates that one state or condition is distinct from, or deviates in some way from, another state or condition.
-
C.
isDifferenceOf
Indicates that one quantity or entity represents the result obtained by subtracting one specified quantity or entity from another.
-
D.
SIBaseUnitRelation
chosen
Indicates a relationship where one physical quantity or unit is defined, measured, or expressed in terms of one or more SI base units.
-
E.
differIn
Indicates that two entities are not the same in at least one specified aspect, attribute, or value.
- 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_69f76ef3b7248190892fb9706423be7c |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbc7b78f9481909f4f8fc2e3fdcde1 |
completed | May 6, 2026, 10:59 p.m. |
| PD | Predicate disambiguation | batch_69fbbd18c9908190928d274f8731dfa8 |
completed | May 6, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:20 p.m.