Triple
T7338651
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Farey tessellation |
E169192
|
entity |
| Predicate | isLocallyFinite |
P77196
|
FINISHED |
| Object | false |
—
|
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: false | Statement: [Farey tessellation, isLocallyFinite, false]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLocallyFinite Context triple: [Farey tessellation, isLocallyFinite, false]
-
A.
isLocallyCompact
Indicates that a topological space has the property that every point has a neighborhood whose closure is compact.
-
B.
isLocallyIsomorphicTo
Indicates that two structures are isomorphic within some local neighborhood or restricted region, even if they may differ globally.
-
C.
finiteAt
Indicates that a function, quantity, or value remains finite (not infinite or undefined) at a specified point or under a given condition.
-
D.
isQuasiCompact
Indicates that a space or object has the property that every open cover admits a finite subcover, or an analogous finiteness/compactness condition in its context.
-
E.
isHausdorff
Indicates that a topological space satisfies the Hausdorff separation property, meaning any two distinct points can be separated by disjoint open sets.
- 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_69c68a57710481909f0c1f3c6ebdb6f2 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f347f25081908e6086d4073295f5 |
completed | March 27, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69c6f028fd748190b2ea5c3081958a42 |
completed | March 27, 2026, 9:01 p.m. |
| PDg | Predicate description generation | batch_69c6f3463d0481908aed9ed43a8ac6a8 |
completed | March 27, 2026, 9:14 p.m. |
Created at: March 27, 2026, 3:04 p.m.