Triple
T31080533
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LLL algorithm |
E792082
|
entity |
| Predicate | deltaRange |
P4679
|
FINISHED |
| Object | delta in (1/4, 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: delta in (1/4, 1) | Statement: [LLL algorithm, deltaRange, delta in (1/4, 1)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deltaRange Context triple: [LLL algorithm, deltaRange, delta in (1/4, 1)]
-
A.
rangeOf
Indicates that one entity specifies the set of possible values (range) that another entity’s outputs or properties can take.
-
B.
coreRange
Indicates the primary spatial or temporal extent within which an entity, phenomenon, or relationship is predominantly present or valid.
-
C.
range
chosen
Indicates that a value, property, or effect extends between specified limits or over a specified interval or scope.
-
D.
displacementRange
Indicates the minimum and maximum extent of positional change or movement that an entity can undergo or exhibits.
-
E.
rangeDownrange
Indicates that one entity is located or directed further along the line of fire or trajectory from another entity, in the downrange direction.
- 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_69f224ccdbbc81909b0cdb4cc2d70c7a |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f695bd88d88190a7bb4fcded6a5b62 |
completed | May 3, 2026, 12:24 a.m. |
| PD | Predicate disambiguation | batch_69f690f13d7481908ddfefe95df2a1c2 |
completed | May 3, 2026, 12:04 a.m. |
Created at: April 29, 2026, 9:02 p.m.