Triple
T24806624
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kronecker pairing |
E620672
|
entity |
| Predicate | isStandardNotation |
P4882
|
FINISHED |
| Object | ⟨·,·⟩ |
—
|
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: ⟨·,·⟩ | Statement: [Kronecker pairing, isStandardNotation, ⟨·,·⟩]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isStandardNotation Context triple: [Kronecker pairing, isStandardNotation, ⟨·,·⟩]
-
A.
isStandard
Indicates that something conforms to an established norm, specification, or commonly accepted rule.
-
B.
isStandardOf
Indicates that something serves as the recognized norm, reference, or benchmark by which another thing is defined, measured, or evaluated.
-
C.
typicalNotation
chosen
Indicates that one entity is the standard or commonly used symbolic representation (notation) for another entity.
-
D.
usesNotationFor
Indicates that one entity employs or adopts a particular notation system or symbolic representation for another entity.
-
E.
isStandardOn
Indicates that a particular feature, option, or component is included by default as part of another item, rather than being optional or extra.
- 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_69e2fabf26bc8190b191faac8f67065b |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f42d9000b8819081ea2605f3c193d6 |
completed | May 1, 2026, 4:35 a.m. |
| PD | Predicate disambiguation | batch_69f420f471a0819095a6cd24ed8f7476 |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 4:50 a.m.