Triple
T30447241
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Supplemental Arrows-A |
E774612
|
entity |
| Predicate | assignedRange |
P160065
|
FINISHED |
| Object | U+27F0–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+27F0–U+27FF | Statement: [Supplemental Arrows-A, assignedRange, U+27F0–U+27FF]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: assignedRange Context triple: [Supplemental Arrows-A, assignedRange, U+27F0–U+27FF]
-
A.
associatedRange
chosen
Indicates that one entity is linked to or falls within a particular range defined or referenced by another entity.
-
B.
alignmentRange
Indicates a relationship where one entity’s alignment or position is constrained to fall within a specified range defined by another entity or set of parameters.
-
C.
designedRange
Indicates the intended or specified range within which something is designed to operate or be effective.
-
D.
rangeOf
Indicates that one entity specifies the set of possible values (range) that another entity’s outputs or properties can take.
-
E.
introducedRange
Indicates that an entity has brought a particular range (such as a span, interval, or set of values) into existence, use, or consideration.
- 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_69f686c07ac48190b5169557e67861c9 |
completed | May 2, 2026, 11:20 p.m. |
| PD | Predicate disambiguation | batch_69f678d2196c8190b9d0d2fcd47cc539 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 29, 2026, 8:09 p.m.