Triple
T31384290
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paczynski–Wiita potential |
E800553
|
entity |
| Predicate | hasSingularityAt |
P4463
|
FINISHED |
| Object | r = r_s |
—
|
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: r = r_s | Statement: [Paczynski–Wiita potential, hasSingularityAt, r = r_s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSingularityAt Context triple: [Paczynski–Wiita potential, hasSingularityAt, r = r_s]
-
A.
hasPhysicalSingularityAt
Indicates that an entity possesses a physical singularity located at a specified point or region in space.
-
B.
hasIsolatedSingularity
Indicates that a function has a singular point at which it is not analytic, but is analytic in some punctured neighborhood around that point.
-
C.
hasSingularityType
Indicates that an entity possesses or is characterized by a specific type or category of singularity.
-
D.
hasCoordinateSingularity
chosen
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.
hasNakedSingularityWhen
Indicates that a system, model, or spacetime configuration possesses a naked singularity under certain specified conditions or circumstances.
- 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_69f224e9d7048190b0cc20f9071bd3e4 |
completed | April 29, 2026, 3:34 p.m. |
| NER | Named-entity recognition | batch_69fcda3699948190adb57625bae08091 |
completed | May 7, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fd16d08190b0aca6e19a632e99 |
completed | May 7, 2026, 6:25 p.m. |
Created at: April 29, 2026, 9:19 p.m.