Triple
T28323556
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 晉 |
E717344
|
entity |
| Predicate | clanStruggle |
P164272
|
FINISHED |
| Object | 六卿專政 |
—
|
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: 六卿專政 | Statement: [晉, clanStruggle, 六卿專政]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: clanStruggle Context triple: [晉, clanStruggle, 六卿專政]
-
A.
clanRival
Indicates a hostile or competitive relationship between two clans, typically involving ongoing conflict, opposition, or rivalry.
-
B.
clanSystem
Indicates a social structure in which individuals are organized into kin-based groups (clans) that define relationships, obligations, and affiliations among them.
-
C.
clanType
Indicates the specific category or classification of a clan within a broader clan system or hierarchy.
-
D.
engagesInCyclicalStruggleWith
Indicates a relationship in which two entities are locked in a recurring, back-and-forth conflict or opposition that repeats over time.
-
E.
clanCentre
Indicates that one entity serves as the central location, headquarters, or main base for a particular clan or group.
- F. None of above. chosen
Provenance (4 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_69eff6e6c3b08190ad78de6ba7f04548 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f6492ce1ec81908f51388ed8eea019 |
completed | May 2, 2026, 6:57 p.m. |
| PD | Predicate disambiguation | batch_69f641e0fde08190bf06a1c5b388aa84 |
completed | May 2, 2026, 6:26 p.m. |
| PDg | Predicate description generation | batch_69f6430975b481909191219ad13ef77e |
completed | May 2, 2026, 6:31 p.m. |
Created at: April 28, 2026, 12:26 a.m.