Triple
T31806640
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vexations |
E811889
|
entity |
| Predicate | hasNotatedInstruction |
P95660
|
FINISHED |
| Object | to be repeated 840 times |
—
|
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: to be repeated 840 times | Statement: [Vexations, hasNotatedInstruction, to be repeated 840 times]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotatedInstruction Context triple: [Vexations, hasNotatedInstruction, to be repeated 840 times]
-
A.
hasInstructionPrefix
Indicates that one entity provides an initial segment or starting portion that serves as the instruction prefix for another entity.
-
B.
hasInstructionModel
Indicates that one entity is associated with, or utilizes, a specific instruction-oriented model to guide its behavior or processing.
-
C.
hasInstructionCache
Indicates that an entity possesses or is equipped with an instruction cache for storing and accessing executable instructions.
-
D.
hasDirective
Indicates that one entity issues, contains, or is governed by a specific directive or instruction associated with another entity.
-
E.
usesNotationFor
chosen
Indicates that one entity employs or adopts a particular notation system or symbolic representation for 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_69f348e70d188190b4637c5509f81274 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a00bcfed6448190b2e816bbe7c61c55 |
completed | May 10, 2026, 5:14 p.m. |
| PD | Predicate disambiguation | batch_6a00bc7be24c81908ba5c1957edd2c10 |
completed | May 10, 2026, 5:12 p.m. |
Created at: April 30, 2026, 11:43 p.m.