Triple
T36491465
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CIDEr |
E899060
|
entity |
| Predicate | metricRange |
P154164
|
FINISHED |
| Object | 0 to 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: 0 to 1 | Statement: [CIDEr, metricRange, 0 to 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: metricRange Context triple: [CIDEr, metricRange, 0 to 1]
-
A.
typicalRange
Indicates the usual or expected range of values, conditions, or states within which something normally occurs or applies.
-
B.
latitudeRangeApproximate
Indicates that the latitude of an entity falls within an approximate or loosely bounded range, rather than an exact or strictly defined interval.
-
C.
typicalRangeClass
Indicates that the related entity belongs to a class whose members typically fall within a characteristic or expected value range.
-
D.
coreRange
Indicates the primary spatial or temporal extent within which an entity, phenomenon, or relationship is predominantly present or valid.
-
E.
rangeDescription
chosen
Indicates the span or interval of values, positions, or extents over which something applies or is valid.
- 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_69f76e5ad4588190bdbce60c52fbb785 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7be9d07ac8190adf796cbef60daf6 |
completed | May 3, 2026, 9:31 p.m. |
| PD | Predicate disambiguation | batch_69f7bccf05bc8190b61fdb2b2a315811 |
completed | May 3, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:10 p.m.