Triple
T31174272
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Φ |
E794697
|
entity |
| Predicate | variantLowercaseUnicodeCodePoint |
P171351
|
FINISHED |
| Object | U+03D5 |
—
|
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+03D5 | Statement: [Φ, variantLowercaseUnicodeCodePoint, U+03D5]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: variantLowercaseUnicodeCodePoint Context triple: [Φ, variantLowercaseUnicodeCodePoint, U+03D5]
-
A.
UnicodeCodePointLowercase
Indicates that one Unicode code point is the lowercase mapping or lowercase equivalent of another code point.
-
B.
ASCIICodeLowercase
Indicates that the ASCII code of one character corresponds to the lowercase form of another character.
-
C.
unicodeCodePoint
Indicates that a character or symbol is associated with a specific Unicode code point value in the Unicode standard.
-
D.
UnicodeCodePointStandard
Indicates that a Unicode code point conforms to, or is defined within, a particular Unicode standard or version.
-
E.
definesCodepoint
Indicates that one entity specifies or assigns the particular codepoint value used to represent another entity in an encoding system.
- F. None of above. chosen
Provenance (4 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_69f224d5b9708190b6ca79ad2fd3a28a |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69f80b62c8190bf2af2be0d3a7df8 |
completed | May 3, 2026, 1:06 a.m. |
| PD | Predicate disambiguation | batch_69f69d1a37e081908d1d86b90ff502bd |
completed | May 3, 2026, 12:55 a.m. |
| PDg | Predicate description generation | batch_69f69dfbf6ac8190ba2e6fc0adfd8b73 |
completed | May 3, 2026, 12:59 a.m. |
Created at: April 29, 2026, 9:07 p.m.