Triple
T33027179
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Electronic Codebook mode |
E845072
|
entity |
| Predicate | blockIndex |
P176090
|
FINISHED |
| Object | i denotes the block number |
—
|
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: i denotes the block number | Statement: [Electronic Codebook mode, blockIndex, i denotes the block number]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: blockIndex Context triple: [Electronic Codebook mode, blockIndex, i denotes the block number]
-
A.
blockNumberInBMP
Indicates that a specific block is located at, or associated with, a particular block number within a BMP (Block Management Plan or similar block-mapped structure).
-
B.
blockReach
Indicates that one block is able to reach or make contact with another block, typically within a defined spatial or interaction range.
-
C.
firstBlockHeight
Indicates the vertical size or elevation of the initial block in a sequence or structure.
-
D.
blocksLeader
Indicates that one entity prevents or obstructs another entity that is in a leadership role from acting or progressing.
-
E.
block
Indicates preventing or obstructing another entity’s action, movement, or access.
- 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_69f34950749c8190ae05cd27adb16d58 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6db6af1d88190989810182354d60f |
completed | May 3, 2026, 5:21 a.m. |
| PD | Predicate disambiguation | batch_69f6d82d068c8190940a3200ed760e38 |
completed | May 3, 2026, 5:07 a.m. |
| PDg | Predicate description generation | batch_69f6db6a38d881909ecc75cc527910f2 |
completed | May 3, 2026, 5:21 a.m. |
Created at: May 1, 2026, 1:23 a.m.