Triple
T24806339
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ivar Bendixson |
E620666
|
entity |
| Predicate | hasNameInCriterion |
P159690
|
FINISHED |
| Object | Bendixson’s criterion |
—
|
NE NERFINISHED |
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: Bendixson’s criterion | Statement: [Ivar Bendixson, hasNameInCriterion, Bendixson’s criterion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNameInCriterion Context triple: [Ivar Bendixson, hasNameInCriterion, Bendixson’s criterion]
-
A.
hasNameInNotation
Indicates that an entity is referred to by a specific name or label within a particular notation or symbolic system.
-
B.
hasNameInCaseTitle
Indicates that a legal case’s title explicitly contains the name of the referenced entity.
-
C.
hasNameInFormula
Indicates that an entity is referred to by a specific name or symbol within a formula or formal expression.
-
D.
hasRuleName
Indicates that an entity is associated with a specific rule identified by a particular name.
-
E.
hasNameFunction
Indicates that an entity is associated with a function whose purpose is to provide or determine its name.
- F. None of above. chosen
Provenance (4 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_69e2fabf26bc8190b191faac8f67065b |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f5f7a205688190b8f36bff5013247c |
completed | May 2, 2026, 1:09 p.m. |
| PD | Predicate disambiguation | batch_69f5afd5baac8190bb8ed576813c8591 |
completed | May 2, 2026, 8:03 a.m. |
| PDg | Predicate description generation | batch_69f5f6b32a8881909baa0db57b80d56a |
completed | May 2, 2026, 1:05 p.m. |
Created at: April 18, 2026, 4:50 a.m.