Triple
T25063672
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Levi-Civita field |
E627727
|
entity |
| Predicate | hasElements |
P63681
|
FINISHED |
| Object | formal power series |
—
|
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: formal power series | Statement: [Levi-Civita field, hasElements, formal power series]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasElements Context triple: [Levi-Civita field, hasElements, formal power series]
-
A.
hasAbstractElements
Indicates that something contains or is composed of non-physical, conceptual, or intangible elements.
-
B.
hasMainElements
Indicates that something possesses or is composed of its primary or most important constituent parts.
-
C.
hasAlternativeElements
Indicates that one entity includes or is associated with elements that can serve as substitutes or options in place of other elements.
-
D.
hasGhostElements
Indicates that an entity contains or is associated with non-physical, hidden, or intangible elements that are not part of its primary visible or material structure.
-
E.
hasElementType
chosen
Indicates that something is composed of or contains elements that are of a specified type.
- 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_69e2ff2d71dc8190b4758e57d643cbe4 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f464b4c9b0819085daa00c7c3b8b76 |
completed | May 1, 2026, 8:30 a.m. |
| PD | Predicate disambiguation | batch_69f45cfb53f4819099bba48c5057e787 |
completed | May 1, 2026, 7:57 a.m. |
Created at: April 18, 2026, 6:10 a.m.