Triple
T36640336
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SL(2,7) |
E904566
|
entity |
| Predicate | hasSimpleQuotient |
P196342
|
FINISHED |
| Object | PSL(2,7) |
—
|
NE NERFINISHED |
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: PSL(2,7) | Statement: [SL(2,7), hasSimpleQuotient, PSL(2,7)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSimpleQuotient Context triple: [SL(2,7), hasSimpleQuotient, PSL(2,7)]
-
A.
hasQuotient
Indicates that one quantity or entity is the result of dividing another quantity or entity by a specified divisor.
-
B.
isQuotientOf
Indicates that one quantity is the result of dividing another quantity by a specified divisor.
-
C.
quotientIs
Indicates that one entity is the result of dividing another entity by a specified divisor (i.e., it represents the quotient in a division relationship).
-
D.
hasQuotientOrder
Indicates that one entity is ordered according to the quotient (or division result) derived from another entity or pair of entities.
-
E.
hasQuotientOrbifold
Indicates that one entity is the quotient orbifold obtained from another entity by taking a group action or identification that forms an orbifold structure.
- 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_69f76e6c63e48190b1d0c3a79a6c7406 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fe21b0cba48190b56c39e9f1c0eafa |
completed | May 8, 2026, 5:47 p.m. |
| PD | Predicate disambiguation | batch_69fe204576848190aecf204e2adba5dc |
completed | May 8, 2026, 5:41 p.m. |
| PDg | Predicate description generation | batch_69fe21afdc4c8190913ac4b55a9a5f52 |
completed | May 8, 2026, 5:47 p.m. |
Created at: May 3, 2026, 4:11 p.m.