Triple
T25063615
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Laurent series |
E627725
|
entity |
| Predicate | expansionPoint |
P134886
|
FINISHED |
| Object | often chosen at an isolated singularity |
—
|
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: often chosen at an isolated singularity | Statement: [Laurent series, expansionPoint, often chosen at an isolated singularity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: expansionPoint Context triple: [Laurent series, expansionPoint, often chosen at an isolated singularity]
-
A.
expansionLocation
Indicates the place or area where something grows, spreads, or extends its presence or influence.
-
B.
expansionAdded
Indicates that an additional component, feature, or content has been incorporated into an existing entity or system.
-
C.
expandsIn
Indicates that one entity grows, spreads, or extends its presence or influence within the space, scope, or context defined by another entity.
-
D.
expansionAround
chosen
Indicates a relationship where one entity grows, spreads, or extends outward from a central point or reference entity.
-
E.
expansionType
Indicates the specific manner or category by which something grows, extends, or increases in scope or size.
- 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_69f4599b7ff081909862edeae57c2c2d |
completed | May 1, 2026, 7:43 a.m. |
| PD | Predicate disambiguation | batch_69f442c861188190967655c6d8012380 |
completed | May 1, 2026, 6:06 a.m. |
Created at: April 18, 2026, 6:10 a.m.