Triple
T16315404
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yi |
E396159
|
entity |
| Predicate | hasTypicalPosition |
P112307
|
FINISHED |
| Object | follows Chinese family name |
—
|
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: follows Chinese family name | Statement: [Yi, hasTypicalPosition, follows Chinese family name]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypicalPosition Context triple: [Yi, hasTypicalPosition, follows Chinese family name]
-
A.
typicalPositionType
chosen
Indicates the usual or most common positional role or placement type that an entity generally occupies or is associated with.
-
B.
typicalPositionsInclude
Indicates that certain positions or roles are commonly or characteristically included within something (such as an organization, structure, or context).
-
C.
hasPositionOn
Indicates that one entity occupies or holds a specific role, job, or spatial location relative to another entity.
-
D.
hasRegionalPosition
Indicates that one entity holds a specific role, status, or placement within a defined geographic or regional context relative to another entity.
-
E.
hasNotablePosition
Indicates that an entity holds or has held a position, role, or office considered notable or significant.
- 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_69d87f255b788190a400eba031dd85d8 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e288de57cc81908cec93309347c385 |
completed | April 17, 2026, 7:24 p.m. |
| PD | Predicate disambiguation | batch_69e219fc72c881909d452274e7af8238 |
completed | April 17, 2026, 11:31 a.m. |
Created at: April 10, 2026, 5:06 a.m.