Triple
T10773173
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grothendieck group |
E254131
|
entity |
| Predicate | outputStructure |
P6556
|
FINISHED |
| Object | abelian group |
—
|
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: abelian group | Statement: [Grothendieck group, outputStructure, abelian group]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: outputStructure Context triple: [Grothendieck group, outputStructure, abelian group]
-
A.
displayStructure
Indicates that one entity presents or reveals the internal organization, layout, or arrangement of another entity.
-
B.
encodingStructure
Indicates the structural scheme or format used to encode information or data.
-
C.
producesStructure
Indicates that one entity generates, forms, or creates a physical or conceptual structure as a result of its action or function.
-
D.
definesStructure
Indicates that one entity specifies or determines the organizational form, composition, or arrangement of another entity.
-
E.
hasOutputStructure
chosen
Indicates that an entity produces, defines, or is associated with a particular structural form or arrangement as its output.
- 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_69d6aa5f54f4819082d0bbcb6f8797e6 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d7329b27748190bd0e2569c7972fd1 |
completed | April 9, 2026, 5:01 a.m. |
| PD | Predicate disambiguation | batch_69d6f31455648190b5c24690487b1b54 |
completed | April 9, 2026, 12:30 a.m. |
Created at: April 8, 2026, 9:16 p.m.