Triple
T7188623
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | kelvin |
E167630
|
entity |
| Predicate | notDegreeSymbol |
P70657
|
FINISHED |
| Object | no degree sign used |
—
|
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: no degree sign used | Statement: [kelvin, notDegreeSymbol, no degree sign used]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notDegreeSymbol Context triple: [kelvin, notDegreeSymbol, no degree sign used]
-
A.
symbolOfTemperature
Indicates that one entity serves as a symbolic representation or notation used to express the temperature of another entity.
-
B.
notAbbreviationOf
Indicates that one term is explicitly asserted not to be an abbreviation or shortened form of another term.
-
C.
doesNotStandFor
Indicates that one entity does not represent, symbolize, or act on behalf of another entity in any capacity.
-
D.
notEncodedIn
chosen
Indicates that a piece of information, data, or content is explicitly absent from or not represented within a given encoding, format, or medium.
-
E.
doesNot
Indicates that a specified entity lacks, refrains from, or fails to perform a particular action or exhibit a particular property in relation to another entity or context.
- 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_69c6888b5248819090499a884ee3ec39 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e8e3d9188190ba2792098d76fb86 |
completed | March 27, 2026, 8:30 p.m. |
| PD | Predicate disambiguation | batch_69c6e752385c819096fbab55566ee2a8 |
completed | March 27, 2026, 8:23 p.m. |
Created at: March 27, 2026, 2:50 p.m.