Triple
T27887491
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Han clan |
E705269
|
entity |
| Predicate | hasPoliticalSystemRole |
P8523
|
FINISHED |
| Object | feudal lords |
—
|
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: feudal lords | Statement: [Han clan, hasPoliticalSystemRole, feudal lords]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPoliticalSystemRole Context triple: [Han clan, hasPoliticalSystemRole, feudal lords]
-
A.
governsInPoliticalSystem
Indicates that one entity exercises authoritative control or rule over another entity within a specified political system or structure.
-
B.
hasGovernmentBodyRole
Indicates that an entity holds or is assigned a specific role or position within a governmental body or institution.
-
C.
hasPoliticalRole
chosen
Indicates that an entity holds, has held, or is assigned a specific political office, function, or position in relation to another entity or context.
-
D.
associatedPoliticalSystem
Indicates that there exists a political system with which the subject is formally or conceptually connected.
-
E.
isInPolity
Indicates that one entity is located within, belongs to, or falls under the jurisdiction of a particular political unit or governing authority.
- 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_69ef96b39c448190a9b3aa6672a5168f |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69fcab6e888881908ca9e18660928a40 |
completed | May 7, 2026, 3:10 p.m. |
| PD | Predicate disambiguation | batch_69fc4562a5b88190bad48f083a6dcdfa |
completed | May 7, 2026, 7:55 a.m. |
Created at: April 27, 2026, 6:34 p.m.