Triple
T27176528
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SL(2,R) |
E683056
|
entity |
| Predicate | nonCompact |
P63679
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [SL(2,R), nonCompact, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nonCompact Context triple: [SL(2,R), nonCompact, true]
-
A.
isNoncompact
chosen
Indicates that the object (such as a space or set) lacks compactness, meaning it does not satisfy the property that every open cover has a finite subcover.
-
B.
nonExclusive
Indicates that the relationship or access is shared among multiple parties and is not limited to a single, exclusive holder.
-
C.
notStandalone
Indicates that an entity cannot exist, function, or be valid independently and must be associated with or supported by another entity.
-
D.
nonperturbativeIn
Indicates that something occurs, is treated, or is valid in a nonperturbative regime or framework within a specified context or system.
-
E.
nonRepresentational
Indicates that the subject lacks representational content or does not depict or stand for anything beyond itself.
- 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_69eefad086808190ab89816c0c300476 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f6257a5ae881908db3032511378836 |
completed | May 2, 2026, 4:25 p.m. |
| PD | Predicate disambiguation | batch_69f620e38aec8190bb184edcdbd6da64 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 27, 2026, 9:26 a.m.