Triple
T31647139
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | join-calculus |
E807610
|
entity |
| Predicate | semanticsBasedOn |
P74447
|
FINISHED |
| Object | reduction rules |
—
|
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: reduction rules | Statement: [join-calculus, semanticsBasedOn, reduction rules]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: semanticsBasedOn Context triple: [join-calculus, semanticsBasedOn, reduction rules]
-
A.
semanticsDetail
Indicates a more specific or fine-grained semantic characterization or nuance of a broader meaning or interpretation.
-
B.
syntaxBasedOn
Indicates that the syntactic structure or rules of one entity are derived from, influenced by, or constructed according to the syntax of another entity.
-
C.
basedOnPhrase
Indicates that something is derived from, inspired by, or constructed using a particular phrase as its source or foundation.
-
D.
hasSemanticsDefinedBy
chosen
Indicates that the meaning or interpretation of one entity is specified, constrained, or determined by another entity.
-
E.
basedOnWord
Indicates that one element is derived from, formed from, or directly influenced by a particular word.
- 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_69f348d9ce58819093ea2da83cbeeec1 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a91f65548190b598917dada0c2c0 |
completed | May 3, 2026, 1:47 a.m. |
| PD | Predicate disambiguation | batch_69f6a757c6e081908e37631e5d8d246b |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 30, 2026, 10:51 p.m.