Triple
T15181939
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Persian satraps |
E362766
|
entity |
| Predicate | couldRebelAgainst |
P107017
|
FINISHED |
| Object | central authority |
—
|
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: central authority | Statement: [Persian satraps, couldRebelAgainst, central authority]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: couldRebelAgainst Context triple: [Persian satraps, couldRebelAgainst, central authority]
-
A.
rebelsAgainst
chosen
Indicates that one entity actively resists, opposes, or rises up against the authority, control, or established order represented by another entity.
-
B.
facedRebellionBy
Indicates that an entity experienced opposition or an uprising initiated by another entity.
-
C.
couldInterveneAgainst
Indicates that one entity has the capability or potential to take action to oppose, prevent, or alter the behavior or effects of another entity.
-
D.
typeOfRebel
Indicates that one entity is a rebel belonging to, or classified under, a particular type or category of rebellion.
-
E.
roleInMutiny
Indicates that one entity participated in a mutiny with a specific role or capacity in that rebellious action.
- 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_69d85a09a39c81908759f23268e2d408 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e006663ad48190986b680001be0e9b |
completed | April 15, 2026, 9:43 p.m. |
| PD | Predicate disambiguation | batch_69deb97bd8bc8190b2ad4888f97cf963 |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:09 a.m.