Triple
T3533729
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John I of Portugal |
E74719
|
entity |
| Predicate | causeOfAccession |
P3715
|
FINISHED |
| Object | crisis of 1383–1385 |
—
|
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: crisis of 1383–1385 | Statement: [John I of Portugal, causeOfAccession, crisis of 1383–1385]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: causeOfAccession Context triple: [John I of Portugal, causeOfAccession, crisis of 1383–1385]
-
A.
reasonForDukedom
Indicates the justification or cause for which a dukedom is granted, held, or recognized.
-
B.
reasonForLossOfSuccessionRights
Indicates the specific cause or circumstance that led to an individual losing their rights of succession.
-
C.
endOfReignReason
Indicates the cause or circumstance that led to the termination of a ruler’s reign.
-
D.
reasonForStartOfReign
chosen
Indicates the cause, circumstance, or event that led to the beginning of an entity’s reign.
-
E.
reasonForAbdication
Indicates the specific cause, motive, or circumstances that led an individual to formally abdicate a position of authority or power.
- 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_69ad85d1a3948190931fd1ea1f49717b |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbc9b945481909867d44b810e8b1f |
completed | March 8, 2026, 6:14 p.m. |
| PD | Predicate disambiguation | batch_69adae13ab808190a5d6ecdc7543445e |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:19 p.m.