Triple
T31992014
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 顏 |
E816896
|
entity |
| Predicate | hasSurnamePosition |
P198360
|
FINISHED |
| Object | precedes given name in Chinese ordering |
—
|
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: precedes given name in Chinese ordering | Statement: [顏, hasSurnamePosition, precedes given name in Chinese ordering]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSurnamePosition Context triple: [顏, hasSurnamePosition, precedes given name in Chinese ordering]
-
A.
hasSurnamePrefix
Indicates that one entity’s surname begins with, or is prefixed by, the string or component specified by the other entity.
-
B.
hasSurnameType
Indicates that an entity’s surname belongs to a particular category or type (e.g., patronymic, toponymic, occupational).
-
C.
hasSurnameRank
Indicates that an entity’s surname holds a particular position or rank within an ordered set, such as a list or hierarchy of surnames.
-
D.
hasSurnamePattern
Indicates that an entity’s surname follows or matches a specified structural or stylistic pattern.
-
E.
hasSeptSurname
Indicates that an entity bears a surname associated with a particular sept (a family subgroup or clan division).
- 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_69f348f8002081909a3588758ba94afb |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fedfd913f48190bdcd450980868d9a |
completed | May 9, 2026, 7:18 a.m. |
| PD | Predicate disambiguation | batch_69fedf58c6e88190821a7156054c9086 |
completed | May 9, 2026, 7:16 a.m. |
| PDg | Predicate description generation | batch_69fedfd850ec81909b55f90dc850167e |
completed | May 9, 2026, 7:18 a.m. |
Created at: May 1, 2026, 12:13 a.m.