Triple
T14387882
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fahrenheit |
E356770
|
entity |
| Predicate | hasBaseInterval |
P114049
|
FINISHED |
| Object | 1 degree Fahrenheit |
—
|
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: 1 degree Fahrenheit | Statement: [Fahrenheit, hasBaseInterval, 1 degree Fahrenheit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBaseInterval Context triple: [Fahrenheit, hasBaseInterval, 1 degree Fahrenheit]
-
A.
hasInterval
Indicates that something is associated with a specific span or range between two points in time, space, or value.
-
B.
hasBaseDate
Indicates that an entity is associated with a specific reference or starting date used as the basis for related calculations, schedules, or validity periods.
-
C.
hasBaseIndex
Indicates that one entity serves as the reference or starting index from which another entity’s position, offset, or ordering is calculated.
-
D.
hasBaseCount
Indicates the number of base units or fundamental components associated with an entity.
-
E.
hasBaselineLength
Indicates that one entity has a specified baseline length measurement in relation to another entity or reference.
- 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_69d827927c988190ad98bb0360981783 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de90283b9c8190b50d30ad58bfe085 |
completed | April 14, 2026, 7:06 p.m. |
| PD | Predicate disambiguation | batch_69de2aa024c48190805df6a9d63deb10 |
completed | April 14, 2026, 11:53 a.m. |
| PDg | Predicate description generation | batch_69de2e08b6c08190bb4c929deab236a6 |
completed | April 14, 2026, 12:07 p.m. |
Created at: April 10, 2026, 1:16 a.m.