Triple
T24810860
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Green's theorem |
E620783
|
entity |
| Predicate | typeOfIntegral |
P162551
|
FINISHED |
| Object | double integral over a planar region |
—
|
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: double integral over a planar region | Statement: [Green's theorem, typeOfIntegral, double integral over a planar region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfIntegral Context triple: [Green's theorem, typeOfIntegral, double integral over a planar region]
-
A.
typeOfIntegral
chosen
Indicates the specific kind or classification of an integral associated with a given mathematical expression or operation.
-
B.
isIntegral
Indicates that a value belongs to the set of integers, having no fractional or decimal component.
-
C.
hasIntegralRepresentation
Indicates that one entity can be expressed or represented as an integral involving the other entity.
-
D.
integralType
Indicates that one entity is an integral (whole) type of which the other is a specific instance, part, or subtype.
-
E.
numericType
Indicates that one entity specifies or constrains the kind or category of numeric value associated with another entity.
- 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_69e2fabf26bc8190b191faac8f67065b |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f62d89b89c8190afb372a8172111e7 |
completed | May 2, 2026, 4:59 p.m. |
| PD | Predicate disambiguation | batch_69f62c1379f08190836c3e02b0c892df |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 18, 2026, 4:50 a.m.