Triple
T31992186
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 鄢 |
E816900
|
entity |
| Predicate | hasSurnameBearers |
P108409
|
FINISHED |
| Object | Chinese individuals and families |
—
|
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: Chinese individuals and families | Statement: [鄢, hasSurnameBearers, Chinese individuals and families]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSurnameBearers Context triple: [鄢, hasSurnameBearers, Chinese individuals and families]
-
A.
hasSurnameBearer
chosen
Indicates that a particular surname is borne or carried by a specific person or entity.
-
B.
hasNameBearersInDynasty
Indicates that the name in question is borne by individuals belonging to a specified dynasty.
-
C.
nameHasMultipleBearers
Indicates that the same name is shared by more than one distinct entity.
-
D.
hasCharacterWithSurname
Indicates that an entity (such as a work or story) includes at least one character whose surname matches the specified name.
-
E.
hasBaseSurname
Indicates that an entity’s surname is derived from, or fundamentally corresponds to, a specified base or canonical surname.
- 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_69fee0b2da3c8190a3519d0564f2f32d |
completed | May 9, 2026, 7:22 a.m. |
| PD | Predicate disambiguation | batch_69fee05b315c819081dfcbfb15273487 |
completed | May 9, 2026, 7:20 a.m. |
Created at: May 1, 2026, 12:13 a.m.