Triple
T31992181
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 鄢 |
E816900
|
entity |
| Predicate | familyNamePosition |
P1082
|
FINISHED |
| Object | placed before given name in Chinese names |
—
|
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: placed before given name in Chinese names | Statement: [鄢, familyNamePosition, placed before given name in Chinese names]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: familyNamePosition Context triple: [鄢, familyNamePosition, placed before given name in Chinese names]
-
A.
familyNamePattern
Indicates that there is a specific structural or formatting pattern that a family name (surname) follows.
-
B.
familyNamePart
Indicates that one string is a component or segment of a person's full family name.
-
C.
familyNameIn
Indicates that an entity has a specified family name (surname) in a particular language or cultural context.
-
D.
laterFamilyNameForm
Indicates that one family name is a later or subsequent form of another family name, reflecting a change or evolution over time.
-
E.
namePosition
chosen
Indicates the positional or ordering relationship of a name within a sequence or structured context (e.g., first, last, or specific index).
- 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_69f348f8002081909a3588758ba94afb |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7764ab1fc81909f9348db87bd7692 |
completed | May 3, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69f76905d9c88190b1ee810bc9ab644f |
completed | May 3, 2026, 3:25 p.m. |
Created at: May 1, 2026, 12:13 a.m.