Triple
T25931703
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AESENCLAST |
E653452
|
entity |
| Predicate | relatedInstruction |
P194547
|
FINISHED |
| Object | AESENC |
—
|
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: AESENC | Statement: [AESENCLAST, relatedInstruction, AESENC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedInstruction Context triple: [AESENCLAST, relatedInstruction, AESENC]
-
A.
relatedRule
Indicates that one rule is connected or associated with another rule, typically through some logical, structural, or referential relationship.
-
B.
includesInstruction
Indicates that one entity contains, provides, or embeds an instruction or set of instructions directed toward another entity.
-
C.
relatedPass
Indicates that one pass is associated with or connected to another pass in some relevant way.
-
D.
relatedGuideline
Indicates that one guideline has a defined relationship or association with another guideline, such as being complementary, dependent, or otherwise contextually linked.
-
E.
relatedRequirement
Indicates that one requirement has a defined relationship or dependency with another requirement.
- F. None of above. chosen
Provenance (4 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_69e7ab3eb9b881909c1390690551f868 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69fd7b0503a08190ba07338365b6fcc9 |
completed | May 8, 2026, 5:56 a.m. |
| PD | Predicate disambiguation | batch_69fd7a9733dc81909199f453c0cc2bc1 |
completed | May 8, 2026, 5:54 a.m. |
| PDg | Predicate description generation | batch_69fd7b042a548190b3abe31bc3258278 |
completed | May 8, 2026, 5:56 a.m. |
Created at: April 22, 2026, 8:37 a.m.