Triple
T32789646
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Galois extension |
E838591
|
entity |
| Predicate | hasExtensionField |
P72945
|
FINISHED |
| Object | larger field |
—
|
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: larger field | Statement: [Galois extension, hasExtensionField, larger field]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasExtensionField Context triple: [Galois extension, hasExtensionField, larger field]
-
A.
hasFieldExtensionDegree
Indicates that one field is an extension of another and specifies the degree (dimension as a vector space) of this extension.
-
B.
hasExtensionBy
Indicates that one entity is extended, augmented, or further developed by another entity.
-
C.
fieldExtensionOf
chosen
Indicates that one field is an extension of another, meaning it contains the smaller field as a subfield and enlarges it by adding new elements while preserving field operations.
-
D.
hasExtensionProject
Indicates that an entity is associated with or participates in a specific extension project.
-
E.
hasExtendedStructure
Indicates that an entity possesses an additional or elongated structural component beyond its basic or standard form.
- 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_69f3493b83f48190be335cd42465cecf |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fb563aec448190875410fb1a3ed624 |
completed | May 6, 2026, 2:54 p.m. |
| PD | Predicate disambiguation | batch_69fb35b9ede881908aaae93a215525df |
completed | May 6, 2026, 12:36 p.m. |
Created at: May 1, 2026, 1:14 a.m.