Triple
T24806619
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kronecker pairing |
E620672
|
entity |
| Predicate | isDefinedAtChainLevelBy |
P96505
|
FINISHED |
| Object | evaluation of cochains on chains |
—
|
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: evaluation of cochains on chains | Statement: [Kronecker pairing, isDefinedAtChainLevelBy, evaluation of cochains on chains]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isDefinedAtChainLevelBy Context triple: [Kronecker pairing, isDefinedAtChainLevelBy, evaluation of cochains on chains]
-
A.
areDefinedIn
Indicates that the referenced entities are specified, described, or formally established within a particular source, context, or scope.
-
B.
wasDefinedBy
Indicates that something was formally specified, described, or established by a particular agent, source, or defining entity.
-
C.
previouslyDefinedIn
Indicates that something has been defined or introduced earlier in time or in a prior context relative to the current reference point.
-
D.
canBeDefinedFor
chosen
Indicates that a certain concept, operation, or property is applicable to and can be meaningfully specified for a given entity or set of entities.
-
E.
endDefinedBy
Indicates that the termination or boundary of one entity is determined, specified, or constrained by another entity.
- 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.