Triple
T26254673
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Khovanov homology |
E656685
|
entity |
| Predicate | isStrongerInvariantThan |
P28230
|
FINISHED |
| Object | Jones polynomial |
—
|
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: Jones polynomial | Statement: [Khovanov homology, isStrongerInvariantThan, Jones polynomial]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isStrongerInvariantThan Context triple: [Khovanov homology, isStrongerInvariantThan, Jones polynomial]
-
A.
isStrongerThan
Indicates that one entity possesses greater physical power, force, or effectiveness than another entity.
-
B.
strongerThan
Indicates that one entity possesses greater strength, power, or intensity than another.
-
C.
invariantOf
Indicates that one element is an invariant (a property or quantity that remains unchanged) with respect to another element, system, or transformation.
-
D.
endedOrWeakenedBy
Indicates that one entity causes the termination or reduction in strength, intensity, or effectiveness of another entity or condition.
-
E.
isMoreSpecificThan
chosen
Indicates that one concept represents a narrower, more detailed, or more constrained case of another concept.
- 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_69ee5b4d25ac819086acb51184602576 |
completed | April 26, 2026, 6:37 p.m. |
| NER | Named-entity recognition | batch_69f60dcd2e688190b54e36b0ff0d9187 |
completed | May 2, 2026, 2:44 p.m. |
| PD | Predicate disambiguation | batch_69f5f7ff548c8190a23e98c5e66e0bc7 |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 26, 2026, 9:08 p.m.