Triple
T25307752
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Daily 3 |
E634526
|
entity |
| Predicate | numberRange |
P28992
|
FINISHED |
| Object | 0-9 |
—
|
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-9 | Statement: [Daily 3, numberRange, 0-9]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberRange Context triple: [Daily 3, numberRange, 0-9]
-
A.
rangeOf
chosen
Indicates that one entity specifies the set of possible values (range) that another entity’s outputs or properties can take.
-
B.
numberVariedBetween
Indicates that the numerical value associated with an entity changed across a specified range between two points or over a given period.
-
C.
includesNumberingRange
Indicates that one entity contains or covers a specified contiguous range of numbers associated with another entity.
-
D.
testRange
Indicates that a value, condition, or behavior is being evaluated to determine whether it falls within a specified range or interval.
-
E.
hasRange
Indicates that a property or relation is constrained to take its values from a specified class, type, or value set.
- 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_69e75a972c6481909bc11710e8d30a6c |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f74062b9388190b30546cf700a825c |
completed | May 3, 2026, 12:32 p.m. |
| PD | Predicate disambiguation | batch_69f73c802b848190b61a416b7488bd96 |
completed | May 3, 2026, 12:16 p.m. |
Created at: April 21, 2026, 1:25 p.m.