Triple
T25433538
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kayles |
E637318
|
entity |
| Predicate | hasOctalCode |
P158504
|
FINISHED |
| Object | 0.77 |
—
|
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: 0.77 | Statement: [Kayles, hasOctalCode, 0.77]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOctalCode Context triple: [Kayles, hasOctalCode, 0.77]
-
A.
hasUnicodeCodePoint
Indicates that a character or symbol is associated with a specific numeric Unicode code point value.
-
B.
hasCanonicalCharacter
Indicates that something is associated with or defined by its standard, officially recognized character representation.
-
C.
hasBlockUnicode
Indicates that one entity possesses or is associated with a specific Unicode block related to another entity.
-
D.
hasFiveCharacterCode
Indicates that an entity is associated with a code consisting of exactly five characters.
-
E.
hasHexCode
Indicates that an entity is associated with a specific hexadecimal color code representing its color value.
- 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_69e75db6c97081908178383fa632b193 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f6dd99f88190848a5bbee795aa17 |
completed | May 2, 2026, 1:06 p.m. |
| PD | Predicate disambiguation | batch_69f4683b34748190818428489a226124 |
completed | May 1, 2026, 8:45 a.m. |
| PDg | Predicate description generation | batch_69f46d361c348190b5fdfd805ecde01b |
completed | May 1, 2026, 9:07 a.m. |
Created at: April 21, 2026, 1:59 p.m.