Triple
T20731156
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sabinada revolt |
E509573
|
entity |
| Predicate | governmentFormClaimed |
P141284
|
FINISHED |
| Object | republic |
—
|
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: republic | Statement: [Sabinada revolt, governmentFormClaimed, republic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governmentFormClaimed Context triple: [Sabinada revolt, governmentFormClaimed, republic]
-
A.
originalClaimedForm
Indicates that one entity is asserted to be the initial or first version/form in which another entity was claimed or presented.
-
B.
legalSystemClaimed
Indicates that a particular legal system asserts authority or jurisdiction over a given entity, situation, or matter.
-
C.
legalClaimBy
Indicates that a specific party initiates or holds a legal claim against another party or concerning a particular matter.
-
D.
governmentFormCreated
Indicates that one entity established or instituted a particular form or system of government for another entity.
-
E.
recordClaim
Indicates that an entity formally documents or logs a claim made by another entity or about a particular matter.
- 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_69e0b4c589c08190834fb5d86d0efa2b |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c1ed7e8c8190974f2eb31a0a3106 |
completed | April 21, 2026, 12:16 a.m. |
| PD | Predicate disambiguation | batch_69e5c04b31248190b9b9d91b5cb854e3 |
completed | April 20, 2026, 5:57 a.m. |
| PDg | Predicate description generation | batch_69e5c3cbe5788190b7ace43bfdac2ef6 |
completed | April 20, 2026, 6:12 a.m. |
Created at: April 16, 2026, 12:30 p.m.