Triple
T38563911
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pepin the Hunchback |
E928163
|
entity |
| Predicate | afterRebellionStatus |
P94217
|
FINISHED |
| Object | confined to a monastery |
—
|
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: confined to a monastery | Statement: [Pepin the Hunchback, afterRebellionStatus, confined to a monastery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: afterRebellionStatus Context triple: [Pepin the Hunchback, afterRebellionStatus, confined to a monastery]
-
A.
endOfRebellion
Indicates that a rebellion or uprising has concluded or been brought to an end.
-
B.
legalStatusAfterCoup
Indicates the legal status or standing of an entity following a coup or unconstitutional change of power.
-
C.
legalStatusAfterWar
Indicates the legal condition or classification assigned to an entity as a consequence of, or following the conclusion of, a war or armed conflict.
-
D.
postRevoltStatus
chosen
Indicates the condition or state of an entity after a revolt or uprising has occurred.
-
E.
afterReformStatus
Indicates the status or condition of an entity following a specified reform or change process.
- 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_69f76eb8d1808190a588af29d8b266d6 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fce28d6c3081908bf76f5db63ecf68 |
completed | May 7, 2026, 7:05 p.m. |
| PD | Predicate disambiguation | batch_69fce12d2f08819082134b5eb3db6a24 |
completed | May 7, 2026, 6:59 p.m. |
Created at: May 3, 2026, 4:32 p.m.