Triple
T9640282
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jintao |
E233044
|
entity |
| Predicate | nameOrderRole |
P28784
|
FINISHED |
| Object | given name in East Asian name order |
—
|
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: given name in East Asian name order | Statement: [Jintao, nameOrderRole, given name in East Asian name order]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nameOrderRole Context triple: [Jintao, nameOrderRole, given name in East Asian name order]
-
A.
namePosition
Indicates the positional or ordering relationship of a name within a sequence or structured context (e.g., first, last, or specific index).
-
B.
namedPersonRole
Indicates that a person is identified by name as holding a specific role or position in a given context.
-
C.
hasNameOrder
chosen
Indicates the specific sequence or arrangement in which the components of a name (e.g., given name, family name, titles) are ordered.
-
D.
orderOrRole
Indicates the hierarchical position, sequence, or functional role that one entity holds relative to others within a structured context.
-
E.
nameType
Indicates the specific category or type of a name associated with an entity (e.g., legal name, nickname, alias, or preferred name).
- 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_69ca848a5a908190aad251f4137b0c3a |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9b552a1c81909a1fab347110eeb1 |
completed | April 1, 2026, 10:25 p.m. |
| PD | Predicate disambiguation | batch_69ccd5b0263081908cf6df3eb07d71b0 |
completed | April 1, 2026, 8:22 a.m. |
Created at: March 30, 2026, 8:12 p.m.