Triple
T9418411
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yong-Quan dialect group |
E227086
|
entity |
| Predicate | hasSpokenFormOnly |
P89040
|
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: [Yong-Quan dialect group, hasSpokenFormOnly, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSpokenFormOnly Context triple: [Yong-Quan dialect group, hasSpokenFormOnly, true]
-
A.
hasSpokenAbout
Indicates that one entity has verbally expressed, discussed, or mentioned another entity or topic.
-
B.
isSpoken
Indicates that a language or utterance is produced orally by a speaker or used in spoken form within a given context.
-
C.
isSpokenAlong
Indicates that something (typically a language or dialect) is used or spoken in the regions or areas that follow a particular path, boundary, or route.
-
D.
usedInSpokenForm
Indicates that something (such as a word, name, or expression) is employed in spoken language or oral communication.
-
E.
isSpokenLanguage
Indicates that a language is used primarily for oral communication by speakers, as opposed to being only written or symbolic.
- 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_69ca84359e7c819091148ba4b670e436 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd68cd1e3481909abcb715e2398120 |
completed | April 1, 2026, 6:49 p.m. |
| PD | Predicate disambiguation | batch_69cca54c37f88190bddccf28e5fe5c84 |
completed | April 1, 2026, 4:55 a.m. |
| PDg | Predicate description generation | batch_69cca9d07eb08190866eb15333386dfa |
completed | April 1, 2026, 5:14 a.m. |
Created at: March 30, 2026, 7:48 p.m.