Triple
T25063587
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Laurent series |
E627725
|
entity |
| Predicate | principalPart |
P158170
|
FINISHED |
| Object | ∑_{n=1}^{∞} a_{-n} (z - z₀)^{-n} |
—
|
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: ∑_{n=1}^{∞} a_{-n} (z - z₀)^{-n} | Statement: [Laurent series, principalPart, ∑_{n=1}^{∞} a_{-n} (z - z₀)^{-n}]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: principalPart
Context triple: [Laurent series, principalPart, ∑_{n=1}^{∞} a_{-n} (z - z₀)^{-n}]
-
A.
mainPartOf
Indicates that one entity is the primary or most significant component of another entity.
-
B.
formerPart
Indicates that an entity was once a component or member of another entity but is no longer part of it.
-
C.
primaryComponent
Indicates that one entity serves as the main or most important component within another entity or system.
-
D.
primaryParticipant
Indicates that an entity plays the main or most central role in a given event, activity, or relationship.
-
E.
primaryGrammaticalBasis
Indicates that one element serves as the main grammatical foundation or core structure upon which another linguistic element is based or constructed.
- 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_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. |
| PDg | Predicate description generation | batch_69f464ae42e88190b3549fdf4e0b425e |
completed | May 1, 2026, 8:30 a.m. |
Created at: April 18, 2026, 6:10 a.m.