Triple
T30447240
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Supplemental Arrows-A |
E774612
|
entity |
| Predicate | blockEnd |
P48547
|
FINISHED |
| Object | U+27FF |
—
|
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+27FF | Statement: [Supplemental Arrows-A, blockEnd, U+27FF]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: blockEnd Context triple: [Supplemental Arrows-A, blockEnd, U+27FF]
-
A.
blockDelimiter
Indicates that one entity serves as a boundary marker that starts, ends, or separates a logical block associated with another entity.
-
B.
functionEnd
Indicates the point or condition at which a function, process, or operation terminates or completes.
-
C.
endOf
chosen
Indicates that one entity marks the terminating point or final boundary of another entity, event, or interval.
-
D.
editorEnd
Indicates that an entity serves as the ending or concluding editor for a work, marking the final editorial responsibility in its production.
-
E.
endRule
Indicates that a previously active rule, regulation, or governing condition is terminated or ceases to apply.
- 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_69f697eabb048190bc01a830f14942c6 |
completed | May 3, 2026, 12:33 a.m. |
| PD | Predicate disambiguation | batch_69f69664142c8190bc695501056b0236 |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 8:09 p.m.