Triple
T21718423
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Unicode 6.1 |
E536089
|
entity |
| Predicate | includesPropertyData |
P86949
|
FINISHED |
| Object | character properties |
—
|
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: character properties | Statement: [Unicode 6.1, includesPropertyData, character properties]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesPropertyData Context triple: [Unicode 6.1, includesPropertyData, character properties]
-
A.
eligibleProperties
Indicates that certain properties meet the required conditions or criteria to qualify for a specified purpose or status.
-
B.
containsDataAbout
chosen
Indicates that one entity holds or includes information or records pertaining to another entity.
-
C.
haveProperty
Indicates that an entity possesses, exhibits, or is characterized by a particular property or attribute.
-
D.
requiresProperty
Indicates that one entity depends on another entity possessing a specific property or attribute in order for a condition, action, or relationship to hold.
-
E.
propertiesType
Indicates that one entity is classified as a specific type or category of properties associated with another entity.
- 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_69e0c46c6dd88190a595375fa6ebd701 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69efd96cc58081908dda09819041b888 |
completed | April 27, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69e6969725bc81908e7ad19619ba2688 |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:47 p.m.