Triple
T7588418
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yìxiān |
E179673
|
entity |
| Predicate | bearerInstanceOf |
P78010
|
FINISHED |
| Object | revolutionary leader |
—
|
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: revolutionary leader | Statement: [Yìxiān, bearerInstanceOf, revolutionary leader]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bearerInstanceOf Context triple: [Yìxiān, bearerInstanceOf, revolutionary leader]
-
A.
bearerType
Indicates the type or category of entity that serves as the bearer or holder in a given relationship or context.
-
B.
bearerField
Indicates that one entity serves as the bearer or holder of a specific field, attribute, or property associated with another entity.
-
C.
bearer
Indicates that one entity carries, holds, or possesses another entity, often as the current holder of a right, document, or object.
-
D.
associatedWithRoleOfNameBearer
Indicates that an entity is connected to or involved with the specific role or function held by a designated name bearer.
-
E.
typicalBearers
Indicates that certain entities are the usual or characteristic holders, users, or possessors of a given property, role, or attribute.
- 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_69c69f335248819093c1006f30513708 |
completed | March 27, 2026, 3:16 p.m. |
| NER | Named-entity recognition | batch_69c6f99875908190b09584cf13ea1e08 |
completed | March 27, 2026, 9:41 p.m. |
| PD | Predicate disambiguation | batch_69c6f4e04c2c8190a889d928515d9b8e |
completed | March 27, 2026, 9:21 p.m. |
| PDg | Predicate description generation | batch_69c6f8184bb08190b2f70545a6aa277c |
completed | March 27, 2026, 9:35 p.m. |
Created at: March 27, 2026, 3:52 p.m.