Triple
T35108705
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 陳其美 |
E1013224
|
entity |
| Predicate | 在組織中角色 |
P13957
|
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: [陳其美, 在組織中角色, 國民黨早期組織建設重要推動者]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 在組織中角色 Context triple: [陳其美, 在組織中角色, 國民黨早期組織建設重要推動者]
-
A.
roleInCommandStructure
Indicates that one entity holds a specific position or function within the hierarchical command structure of another entity or organization.
-
B.
hasOrganizationalRole
chosen
Indicates that an entity holds a specific role, position, or function within an organization.
-
C.
roleInTaiwan
Indicates that an entity holds or has held an official or notable role, position, or function within the political, administrative, or social context of Taiwan.
-
D.
hasRoleInFormationOf
Indicates that an entity plays a specific role or function in the creation, development, or establishment of another entity or structure.
-
E.
roleInPersonnelMatters
Indicates that one entity has a specific function, authority, or involvement in managing or deciding personnel-related matters concerning another entity.
- 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_69f76dd659d08190bcdc00d37caafb62 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78ce78b508190955848e133398dc8 |
completed | May 3, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69f78b8f4cc08190b49fccd798cb25d7 |
completed | May 3, 2026, 5:53 p.m. |
Created at: May 3, 2026, 4:01 p.m.