Triple
T7338464
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jones polynomial |
E169187
|
entity |
| Predicate | variableConvention |
P55768
|
FINISHED |
| Object | q |
—
|
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: q | Statement: [Jones polynomial, variableConvention, q]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: variableConvention Context triple: [Jones polynomial, variableConvention, q]
-
A.
namingConventionType
chosen
Indicates the specific style or set of rules used for naming entities or elements in a given context.
-
B.
logicConvention
Indicates a relationship where entities participate in or are associated with a convention, event, or standard related to logic or logical systems.
-
C.
visualConvention
Indicates a conventional or commonly accepted way of visually representing or depicting something, rather than a literal or unique visual form.
-
D.
constantName
Indicates that an entity has a specific, fixed identifier or label used as a constant within a system or context.
-
E.
signingConvention
Indicates that one party formally agrees to and adopts the terms of a convention, treaty, or formal agreement.
- 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_69c68a57710481909f0c1f3c6ebdb6f2 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f347f25081908e6086d4073295f5 |
completed | March 27, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69c6f028fd748190b2ea5c3081958a42 |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:04 p.m.