Triple
T24493891
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | T$ |
E617724
|
entity |
| Predicate | hasUnicodeCharacters |
P16918
|
FINISHED |
| Object | U+0054 (T) |
—
|
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: U+0054 (T) | Statement: [T$, hasUnicodeCharacters, U+0054 (T)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUnicodeCharacters Context triple: [T$, hasUnicodeCharacters, U+0054 (T)]
-
A.
hasUnicode
chosen
Indicates that an entity is associated with, represented by, or encoded using a specific Unicode character or sequence.
-
B.
hasUnicodeStatus
Indicates that a given entity has a particular Unicode-related classification or status (such as assigned, reserved, deprecated, or noncharacter) within the Unicode standard.
-
C.
hasUnicodeChart
Indicates that an entity is associated with, documented in, or represented by a specific Unicode character chart or code chart.
-
D.
hasUnicodeStandard
Indicates that something conforms to, is defined by, or is associated with a particular version or aspect of the Unicode standard.
-
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_69e2d7f4e6bc8190aec540ae3b9ed7f2 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f2a9d912e88190bc39c05a9d7f407e |
completed | April 30, 2026, 1:01 a.m. |
| PD | Predicate disambiguation | batch_69f2a6a4580481908fddc385f5262f95 |
completed | April 30, 2026, 12:47 a.m. |
Created at: April 18, 2026, 2:22 a.m.