Triple
T6282328
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lie ring |
E140808
|
entity |
| Predicate | hasZeroBracketExample |
P1259
|
FINISHED |
| Object | abelian Lie ring |
—
|
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 Lie ring | Statement: [Lie ring, hasZeroBracketExample, abelian Lie ring]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasZeroBracketExample Context triple: [Lie ring, hasZeroBracketExample, abelian Lie ring]
-
A.
hasBracket
Indicates that one entity possesses, includes, or is associated with a bracket component or structure.
-
B.
hasExample
chosen
Indicates that one entity serves as an instance, illustration, or concrete example of another entity.
-
C.
hasNonExample
Indicates that something is associated with an instance that explicitly does not satisfy or illustrate a given concept, rule, or category.
-
D.
hasCounterexample
Indicates that there exists at least one specific case or instance that disproves or violates a given claim, rule, or general statement.
-
E.
isZeroFor
Indicates that a given value, expression, or function evaluates to zero when applied to or considered with respect to a specified entity or context.
- 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_69c008cd17c8819082b82d3fbeb68047 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c063f956c08190ae0f198ccbd68b42 |
completed | March 22, 2026, 9:49 p.m. |
| PD | Predicate disambiguation | batch_69c05608a5608190b22a1fdc4060470d |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:26 p.m.