Triple
T2980982
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mem |
E80508
|
entity |
| Predicate | categoryInUnicode |
P1445
|
FINISHED |
| Object | Letter |
—
|
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: Letter | Statement: [Mem, categoryInUnicode, Letter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: categoryInUnicode Context triple: [Mem, categoryInUnicode, Letter]
-
A.
isocodeCategory
Indicates that an entity is classified under a specific ISO code category or grouping.
-
B.
UnicodeBlock
chosen
Indicates that a character belongs to a specific contiguous range of code points defined as a Unicode block.
-
C.
uniformCategory
Indicates that two or more entities share the same classification or type within a defined category system.
-
D.
relationshipToUnicode
Indicates a mapping or association between an entity and its corresponding Unicode representation or code point.
-
E.
hasUnicodeName
Indicates that an entity is associated with a specific official Unicode name assigned to a character or symbol.
- 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_69ad8b15f6ac8190be5fd16a33edcb4f |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad999e91788190a2d430dd0600a660 |
completed | March 8, 2026, 3:45 p.m. |
| PD | Predicate disambiguation | batch_69ad9611fc348190a5d17d237f653f60 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 2:58 p.m.