Triple
T18564498
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PUA-B |
E453727
|
entity |
| Predicate | hasStandardName |
P71820
|
FINISHED |
| Object | Supplementary Private Use Area-B |
—
|
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: Supplementary Private Use Area-B | Statement: [PUA-B, hasStandardName, Supplementary Private Use Area-B]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStandardName Context triple: [PUA-B, hasStandardName, Supplementary Private Use Area-B]
-
A.
hasStandardizedNameInEnglish
chosen
Indicates that an entity is associated with a specific standardized or officially recognized name expressed in English.
-
B.
hasProperName
Indicates that an entity is associated with a specific proper name used to uniquely identify it.
-
C.
isStandard
Indicates that something conforms to an established norm, specification, or commonly accepted rule.
-
D.
hasNameCharacteristic
Indicates that an entity possesses a specific quality or attribute related to its name.
-
E.
hasStandardCode
Indicates that an entity is associated with a recognized standard code that formally identifies or classifies it.
- 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_69d8d38974308190a9174430ef256b73 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e53afd8114819093b57d86f8213311 |
completed | April 19, 2026, 8:28 p.m. |
| PD | Predicate disambiguation | batch_69e478c16e0c8190b03966aa23c395a6 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:42 a.m.