Triple
T10991528
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Henstock–Kurzweil integral |
E259763
|
entity |
| Predicate | definitionBasedOn |
P57965
|
FINISHED |
| Object | tagged partitions |
—
|
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: tagged partitions | Statement: [Henstock–Kurzweil integral, definitionBasedOn, tagged partitions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definitionBasedOn Context triple: [Henstock–Kurzweil integral, definitionBasedOn, tagged partitions]
-
A.
basedOnBy
Indicates that one entity is derived from, justified by, or constructed using another entity as its source, foundation, or reference.
-
B.
defined
Indicates that one entity specifies, explains, or establishes the meaning, scope, or identity of another entity.
-
C.
isBasedOn
Indicates that one entity is derived from, inspired by, or developed using the content, structure, or principles of another entity.
-
D.
definitionType
chosen
Indicates the specific kind or category of definition that characterizes how one entity is defined in relation to another.
-
E.
definitionText
Indicates the textual content that provides the definition or explanatory meaning of a concept, term, or 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_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. |
Created at: April 8, 2026, 9:24 p.m.