Triple
T17006462
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jyutping |
E412583
|
entity |
| Predicate | usesToneNumbers |
P126167
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Jyutping, usesToneNumbers, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesToneNumbers Context triple: [Jyutping, usesToneNumbers, true]
-
A.
usesNumeralsFrom
Indicates that one writing system, notation, or representation employs the numeral symbols originating from another system.
-
B.
telephoneStandard
Indicates that there is a relationship involving the use of a particular telephone standard or protocol for communication between entities.
-
C.
usesOpenNumberingPlan
Indicates that a telecommunication system or region employs an open numbering plan, where phone numbers can vary in length rather than following a fixed-length format.
-
D.
usesClosedNumberingPlan
Indicates that a telecommunication system or network follows a closed numbering plan, where phone numbers have fixed lengths and formats without requiring variable-length dialing.
-
E.
supportsTone
Indicates that one entity is compatible with, enables, or can correctly handle a specified tone or tonal characteristic of another entity.
- 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_69d886cb581c8190ab05f4b429c9cd85 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d3831268819089286053a5acf653 |
completed | April 18, 2026, 6:54 p.m. |
| PD | Predicate disambiguation | batch_69e35d552bc08190af17ef7659e094ef |
completed | April 18, 2026, 10:30 a.m. |
| PDg | Predicate description generation | batch_69e378e037c88190935d732e0f10d5d7 |
completed | April 18, 2026, 12:28 p.m. |
Created at: April 10, 2026, 5:32 a.m.