Triple
T23387496
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PUA-A |
E593923
|
entity |
| Predicate | hasGeneralCategoryDescription |
P11875
|
FINISHED |
| Object | Other, private use |
—
|
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: Other, private use | Statement: [PUA-A, hasGeneralCategoryDescription, Other, private use]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGeneralCategoryDescription Context triple: [PUA-A, hasGeneralCategoryDescription, Other, private use]
-
A.
hasDescription
chosen
Indicates that an entity is associated with a textual description that explains or characterizes it.
-
B.
hasMeaningCategory
Indicates that something is associated with a particular category of meaning or semantic type.
-
C.
hasGeneralPurpose
Indicates that one entity serves as the broad, overarching function, role, or intended use of another entity.
-
D.
hasSpecialCategory
Indicates that an entity is associated with a designated special or exceptional category distinct from its standard classifications.
-
E.
category4Description
Indicates the detailed textual description associated with a fourth-level or type-4 category in a classification or grouping system.
- 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_69e25d2754fc819085deea939bde60ab |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1a498fd08819085e90a872d9d0c7a |
completed | April 29, 2026, 6:26 a.m. |
| PD | Predicate disambiguation | batch_69f061dde2e481908308952f9c0d3c2e |
completed | April 28, 2026, 7:29 a.m. |
Created at: April 17, 2026, 5:35 p.m.