Triple
T24824322
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Combinatorial Nullstellensatz |
E621146
|
entity |
| Predicate | statedOver |
P147184
|
FINISHED |
| Object | commutative 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: commutative field | Statement: [Combinatorial Nullstellensatz, statedOver, commutative field]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statedOver Context triple: [Combinatorial Nullstellensatz, statedOver, commutative field]
-
A.
statedFor
chosen
Indicates that something has been explicitly declared, specified, or asserted in reference to a particular entity, context, or condition.
-
B.
locatedOver
Indicates that one entity is positioned above another entity, typically without direct contact, in a vertical or overhead spatial relationship.
-
C.
oftenStatedWith
Indicates that one statement, fact, or expression is frequently mentioned or asserted together with another.
-
D.
holdsOver
Indicates that a certain condition, state, or relationship remains valid or continues to apply across a specified period, context, or range.
-
E.
over
Indicates that one entity is positioned higher than and extending across or above another entity, often covering or spanning it.
- 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_69e2fac0c3b881909110e5a56c6fa46f |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f453035f508190be83a3d521723acf |
completed | May 1, 2026, 7:15 a.m. |
| PD | Predicate disambiguation | batch_69f44d6ef33081908f5d36ba1ae5f473 |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 18, 2026, 5:05 a.m.