Triple
T10991470
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Simpson's rule |
E259761
|
entity |
| Predicate | integrationIntervalNotation |
P96503
|
FINISHED |
| Object | [a,b] |
—
|
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: [a,b] | Statement: [Simpson's rule, integrationIntervalNotation, [a,b]]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: integrationIntervalNotation Context triple: [Simpson's rule, integrationIntervalNotation, [a,b]]
-
A.
invariantInterval
Indicates that a certain interval or range remains unchanged or constant under a specified transformation or set of conditions.
-
B.
integralTo
Indicates that one entity is an essential, non-removable component or part of another entity, such that the whole depends on it to function or be complete.
-
C.
intervalAct
Indicates an action or relationship that occurs over, or is defined by, a specific time interval between entities.
-
D.
integralVersionUsedIn
Indicates that a specific integral version (e.g., of a component, document, or artifact) is utilized within or by another entity or process.
-
E.
zeroSetNotation
Indicates that something is expressed or represented using the notation for the set containing only the element zero.
- 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_69d6aa8a6a548190a750f944ccdc8064 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d795d1e918819090c71f5a077fa15a |
completed | April 9, 2026, 12:04 p.m. |
| PD | Predicate disambiguation | batch_69d72e93ac648190b46c5d12bf3eb1e9 |
completed | April 9, 2026, 4:44 a.m. |
| PDg | Predicate description generation | batch_69d732242fdc8190be77d1f730a42935 |
completed | April 9, 2026, 4:59 a.m. |
Created at: April 8, 2026, 9:24 p.m.