Triple
T6833466
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bernoulli lemniscate |
E157392
|
entity |
| Predicate | selfIntersectionPoint |
P50696
|
FINISHED |
| Object | (0,0) |
—
|
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: (0,0) | Statement: [Bernoulli lemniscate, selfIntersectionPoint, (0,0)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: selfIntersectionPoint Context triple: [Bernoulli lemniscate, selfIntersectionPoint, (0,0)]
-
A.
hasCrossingPoint
chosen
Indicates that two or more entities intersect or share at least one common point in space or along their paths.
-
B.
hadCrossingPoints
Indicates that two entities intersected or overlapped at one or more specific points in space or time.
-
C.
hasInflectionPointsAt
Indicates that a function or curve has inflection points located at the specified positions or values.
-
D.
hasCoordinateSingularity
Indicates that something possesses a point or region where its coordinate description becomes undefined or degenerate, even if the underlying object or space may remain well-behaved.
-
E.
locatedAtIntersectionOf
Indicates that something is situated at the point where two or more paths, roads, or boundaries cross or meet.
- 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_69c6882c53608190b99aebef079b23bd |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d62b1e8c8190a81d91191a54b073 |
completed | March 27, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69c6d09d95f0819091ca7f897dc21efe |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:18 p.m.