Triple
T32508173
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wu Guang |
E830856
|
entity |
| Predicate | roleInUprising |
P88009
|
FINISHED |
| Object | military commander |
—
|
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: military commander | Statement: [Wu Guang, roleInUprising, military commander]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInUprising Context triple: [Wu Guang, roleInUprising, military commander]
-
A.
roleInRevolt
chosen
Indicates the specific function, position, or level of participation an entity had within a particular revolt or uprising.
-
B.
roleInRiseAgainst
Indicates that an entity held a specific role or position within the group or organization known as Rise Against.
-
C.
socialMovementRole
Indicates the specific function, position, or responsibility an entity holds within a social movement.
-
D.
roleInMutiny
Indicates that one entity participated in a mutiny with a specific role or capacity in that rebellious action.
-
E.
roleInAmericanRevolution
Indicates that an entity had a specific role, position, or involvement in events or activities related to the American Revolution.
- 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_69f3492318348190ba37fb6b5f1d67f4 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a0031ed5d708190ab93516ad081ada6 |
completed | May 10, 2026, 7:21 a.m. |
| PD | Predicate disambiguation | batch_6a0031b5dbd081908eb0f4dbb8a0eac3 |
completed | May 10, 2026, 7:20 a.m. |
Created at: May 1, 2026, 1 a.m.