Triple
T8454730
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Menger curvature |
E199891
|
entity |
| Predicate | hasIntegralVersion |
P71171
|
FINISHED |
| Object | integral Menger curvature |
—
|
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: integral Menger curvature | Statement: [Menger curvature, hasIntegralVersion, integral Menger curvature]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIntegralVersion Context triple: [Menger curvature, hasIntegralVersion, integral Menger curvature]
-
A.
hasVersionNumber
Indicates that an entity is associated with a specific version identifier or number.
-
B.
hasStandardVersion
Indicates that one entity serves as the official or canonical version of another entity.
-
C.
hasIntegralRepresentation
chosen
Indicates that one entity can be expressed or represented as an integral involving the other entity.
-
D.
hasVersionIn
Indicates that one entity exists as a specific version or variant within the context, format, or system represented by another entity.
-
E.
hasVersionType
Indicates that one entity is associated with a specific kind or category of version of 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_69ca8318231881908fd1bc1c4d45d286 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe48ca9988190b60ebd09a135194d |
completed | March 31, 2026, 3:13 p.m. |
| PD | Predicate disambiguation | batch_69cbd0fc634481909842c0a30077bfde |
completed | March 31, 2026, 1:49 p.m. |
Created at: March 30, 2026, 6:10 p.m.