Triple
T33312410
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Singular |
E852920
|
entity |
| Predicate | hasMainApplicationArea |
P148271
|
FINISHED |
| Object | commutative algebra |
—
|
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: commutative algebra | Statement: [Singular, hasMainApplicationArea, commutative algebra]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainApplicationArea Context triple: [Singular, hasMainApplicationArea, commutative algebra]
-
A.
isOneOfMainAreasFor
chosen
Indicates that something belongs to the primary set of domains, topics, or fields associated with another entity.
-
B.
hasCoreArea
Indicates that an entity possesses a primary or central area that is fundamental to its structure, function, or focus.
-
C.
hasPrimaryServiceArea
Indicates that an entity is associated with a main geographic or functional area in which it primarily provides its services.
-
D.
hasMainArch
Indicates that an entity possesses or features a primary or central arch structure.
-
E.
hasMainLocationType
Indicates that an entity is associated with a primary or predominant type of location that characterizes where it is mainly situated or operates.
- 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_69f349679fd8819093b9b40e989440e3 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a00d6aff0a08190a330dd0c7c1352f9 |
completed | May 10, 2026, 7:04 p.m. |
| PD | Predicate disambiguation | batch_6a00d60f2a508190aeaf5a9d8af9c39e |
completed | May 10, 2026, 7:01 p.m. |
Created at: May 1, 2026, 1:33 a.m.