Triple
T7338238
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Co1 |
E169183
|
entity |
| Predicate | hasAutomorphismGroup |
P14251
|
FINISHED |
| Object | Co1·2 |
E169183
|
NE 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: Co1·2 | Statement: [Co1, hasAutomorphismGroup, Co1·2]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Co1·2 Context triple: [Co1, hasAutomorphismGroup, Co1·2]
-
A.
Co1
chosen
Co1 is the largest of the three sporadic Conway groups, a finite simple group arising as a symmetry group related to the Leech lattice in 24-dimensional space.
-
B.
Co3
Co3 is one of the three sporadic Conway simple groups, notable as a finite simple group related to the symmetries of the Leech lattice.
-
C.
CL-CO
CL-CO is the ISO 3166-2 subdivision code assigned to the commune of Salamanca in Chile’s Coquimbo Region.
-
D.
Coe
Coe is a surname most prominently associated with Sebastian Coe, the British middle-distance running champion and influential sports administrator.
-
E.
CO-ANT
CO-ANT is the administrative region code for the Antioquia Department in Colombia, used to identify municipalities such as Turbo within that jurisdiction.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69c68a57710481909f0c1f3c6ebdb6f2 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f0d599c88190875514eae7084f8d |
completed | March 27, 2026, 9:04 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c7ef266fd0819096cf3ece3fff6b90 |
completed | March 28, 2026, 3:09 p.m. |
Created at: March 27, 2026, 3:04 p.m.