Triple
T26220548
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Proclamation of Accession |
E655752
|
entity |
| Predicate | followsImmediately |
P50088
|
FINISHED |
| Object | accession of the monarch in law |
—
|
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: accession of the monarch in law | Statement: [Proclamation of Accession, followsImmediately, accession of the monarch in law]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followsImmediately Context triple: [Proclamation of Accession, followsImmediately, accession of the monarch in law]
-
A.
followsBetween
Indicates that one entity comes after or succeeds another entity within a specified context or sequence.
-
B.
followsIn
Indicates that one entity comes after or succeeds another in a sequence, order, or progression.
-
C.
followsBy
chosen
Indicates that one event, state, or entity occurs or comes immediately after another in a sequence or order.
-
D.
followsTo
Indicates that one entity moves or proceeds behind another entity toward a specific destination or target.
-
E.
follows
Indicates that one entity comes after, moves behind, or acts in accordance with another entity in time, space, or sequence.
- 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_69ee5b4a77e08190bfcb5f8ecdc55abd |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f676c440708190a4b9974e95d2291a |
completed | May 2, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69f675fd59608190b246383435e68fce |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 26, 2026, 8:55 p.m.