Triple
T31829091
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yuanh |
E812475
|
entity |
| Predicate | notStandardIn |
P75395
|
FINISHED |
| Object | Hanyu Pinyin |
—
|
NE NERFINISHED |
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: Hanyu Pinyin | Statement: [Yuanh, notStandardIn, Hanyu Pinyin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notStandardIn Context triple: [Yuanh, notStandardIn, Hanyu Pinyin]
-
A.
notStandardizedBy
Indicates that an entity has not been brought into conformity with a particular standard, method, or specification by the referenced agent or authority.
-
B.
notOfficialIn
chosen
Indicates that an entity does not hold an official role, status, or position within a specified organization, group, or jurisdiction.
-
C.
notTypically
Indicates that the referenced situation, behavior, or relationship does not usually or normally occur under standard or expected conditions.
-
D.
notStandalone
Indicates that an entity cannot exist, function, or be valid independently and must be associated with or supported by another entity.
-
E.
notStatus
Indicates that an entity does not have, is not in, or does not match a specified status or state.
- 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_69f348e97fa48190aa06286962af6dee |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6af8748bc8190bfe1afc840501273 |
completed | May 3, 2026, 2:14 a.m. |
| PD | Predicate disambiguation | batch_69f6aca59d4881908d14ed47962703bd |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 30, 2026, 11:47 p.m.