Triple
T32100771
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ji |
E819841
|
entity |
| Predicate | hasNamingType |
P2396
|
FINISHED |
| Object | xing (clan name) |
—
|
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: xing (clan name) | Statement: [Ji, hasNamingType, xing (clan name)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNamingType Context triple: [Ji, hasNamingType, xing (clan name)]
-
A.
hasNaming
Indicates that one entity assigns, bears, or is associated with a specific name or designation provided by another entity.
-
B.
hasTypeName
chosen
Indicates that an entity is associated with a specific type name used to classify or identify its kind.
-
C.
hasTypeOfNames
Indicates that one entity possesses or is associated with a particular category or kind of names defined by another entity.
-
D.
hasNameElementType
Indicates that something includes a specific type or category of element within its name.
-
E.
usesNamingSystem
Indicates that one entity adopts or applies a particular naming system or convention to identify or label other entities.
- 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_69f34901106881908ea893ad504a08be |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fe6fea4a288190bf8615c5d6bf41b4 |
completed | May 8, 2026, 11:21 p.m. |
| PD | Predicate disambiguation | batch_69fe6f774de08190975a2393b9a1fd22 |
completed | May 8, 2026, 11:19 p.m. |
Created at: May 1, 2026, 12:26 a.m.