Triple
T1483868
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Conway polynomial |
E29419
|
entity |
| Predicate | doesNotCompletelyClassify |
P19089
|
FINISHED |
| Object | knots |
—
|
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: knots | Statement: [Conway polynomial, doesNotCompletelyClassify, knots]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: doesNotCompletelyClassify Context triple: [Conway polynomial, doesNotCompletelyClassify, knots]
-
A.
notClassifiedAs
Indicates that an entity is explicitly not assigned to, or excluded from, a particular class or category.
-
B.
doesNotDetermine
chosen
Indicates that one entity or factor does not uniquely fix, decide, or specify the state, value, or outcome of another.
-
C.
isSometimesClassifiedAs
Indicates that an entity is occasionally, but not consistently or universally, categorized under a particular type or class.
-
D.
doesNotFullyExplain
Indicates that one entity’s explanation of another entity, event, or situation is incomplete or insufficient to account for it fully.
-
E.
doesNot
Indicates that a specified entity lacks, refrains from, or fails to perform a particular action or exhibit a particular property in relation to another 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_69a498da82e08190ba833330d05f380f |
completed | March 1, 2026, 7:51 p.m. |
| NER | Named-entity recognition | batch_69a4c679714c8190ac53630fb49e19c5 |
completed | March 1, 2026, 11:06 p.m. |
| PD | Predicate disambiguation | batch_69a4c486eacc81909c272f9bdf50a7c3 |
completed | March 1, 2026, 10:58 p.m. |
Created at: March 1, 2026, 8:12 p.m.