Triple
T24805957
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Runge phenomenon |
E620658
|
entity |
| Predicate | typicalExampleInterval |
P167029
|
FINISHED |
| Object | [-1, 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: [-1, 1] | Statement: [Runge phenomenon, typicalExampleInterval, [-1, 1]]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalExampleInterval Context triple: [Runge phenomenon, typicalExampleInterval, [-1, 1]]
-
A.
typicalPeriod
Indicates the usual or characteristic time interval or duration associated with an event, process, or state.
-
B.
typicalPeriodRange
Indicates the usual or most commonly observed range of time intervals associated with an event, process, or state.
-
C.
typicalTimes
Indicates the usual or characteristic times at which an event, activity, or condition typically occurs.
-
D.
typicalStartPeriod
Indicates the usual or standard time period during which something begins or is initiated.
-
E.
intervalPattern
Indicates a recurring temporal relationship where events or states follow a specific, regular interval pattern between their occurrences.
- 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_69e2fabf26bc8190b191faac8f67065b |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f6653ccf648190b65fb1141928e47e |
completed | May 2, 2026, 8:57 p.m. |
| PD | Predicate disambiguation | batch_69f6633451948190bcc0410602bb4914 |
completed | May 2, 2026, 8:48 p.m. |
| PDg | Predicate description generation | batch_69f663ff176c8190aaadb475f75daee4 |
completed | May 2, 2026, 8:52 p.m. |
Created at: April 18, 2026, 4:50 a.m.