Triple
T6833485
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bernoulli lemniscate |
E157392
|
entity |
| Predicate | loopLocation |
P72978
|
FINISHED |
| Object | one loop in right half-plane |
—
|
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: one loop in right half-plane | Statement: [Bernoulli lemniscate, loopLocation, one loop in right half-plane]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: loopLocation Context triple: [Bernoulli lemniscate, loopLocation, one loop in right half-plane]
-
A.
loopType
Indicates the specific kind or category of loop structure or iteration pattern used in a process or control flow.
-
B.
isLoop
Indicates that something forms or behaves as a closed, repeating cycle or path that returns to its starting point.
-
C.
repeatLocation
Indicates that an entity occurs or appears multiple times at the same location or position.
-
D.
formsLoopAround
Indicates that one entity extends or curves so as to create a closed loop encircling or surrounding another entity or region.
-
E.
reentryLocation
Indicates the place or area where an entity returns or re-enters after having left or exited a previous location or state.
- 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_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. |
| PDg | Predicate description generation | batch_69c6d11fab808190b18160ff3829fcc6 |
completed | March 27, 2026, 6:49 p.m. |
Created at: March 27, 2026, 2:18 p.m.