Triple
T22891464
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Unicode Standard |
E568049
|
entity |
| Predicate | firstPlaneRange |
P150147
|
FINISHED |
| Object | 0x0000–0xFFFF |
—
|
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: 0x0000–0xFFFF | Statement: [The Unicode Standard, firstPlaneRange, 0x0000–0xFFFF]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstPlaneRange Context triple: [The Unicode Standard, firstPlaneRange, 0x0000–0xFFFF]
-
A.
flightRangeFocus
Indicates that the relationship centers on the range or distance a flight can cover, emphasizing limitations or focus on how far the flight can travel.
-
B.
firstFlightDistance
Indicates the distance covered during an entity’s first recorded flight.
-
C.
aircraftRangeCategory
Indicates the classification of an aircraft based on the distance it is capable of flying on a typical mission or with standard fuel capacity.
-
D.
aircraftDesignRange
Indicates the maximum distance an aircraft is designed to fly under specified conditions without refueling.
-
E.
firstFlightType
Indicates the category or nature of an entity’s initial flight (e.g., test, commercial, cargo, passenger).
- 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_69e2458c23ec81908fa2570692c6614f |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f17fc59e108190a22f90c2439830fb |
completed | April 29, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69ef3b6b2e2481908258156937b5a745 |
completed | April 27, 2026, 10:33 a.m. |
| PDg | Predicate description generation | batch_69ef538a115081908982597f79355840 |
completed | April 27, 2026, 12:16 p.m. |
Created at: April 17, 2026, 3:40 p.m.