Triple
T30447239
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Supplemental Arrows-A |
E774612
|
entity |
| Predicate | blockStart |
P64686
|
FINISHED |
| Object | U+27F0 |
—
|
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: U+27F0 | Statement: [Supplemental Arrows-A, blockStart, U+27F0]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: blockStart Context triple: [Supplemental Arrows-A, blockStart, U+27F0]
-
A.
blockStartHex
Indicates the starting position or address of a data block, expressed in hexadecimal form.
-
B.
blockDelimiter
Indicates that one entity serves as a boundary marker that starts, ends, or separates a logical block associated with another entity.
-
C.
block
Indicates preventing or obstructing another entity’s action, movement, or access.
-
D.
blockType
Indicates that one entity is classified as a specific type or category of block in relation to another entity.
-
E.
startBoundary
chosen
Indicates the point, limit, or marker where something begins or where a specified interval, region, or process first comes into effect.
- 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_69f22493ef9c8190ae8c2afcb7f994c8 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6953bafb88190a860e9c68a3dd4b2 |
completed | May 3, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69f690ed5d008190831cf8e44cce28af |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 29, 2026, 8:09 p.m.