Triple
T172309
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pragmatic Sanction of 1713 |
E3501
|
entity |
| Predicate | predecessorLawModified |
P7980
|
FINISHED |
| Object | Habsburg agnatic succession rules |
—
|
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: Habsburg agnatic succession rules | Statement: [Pragmatic Sanction of 1713, predecessorLawModified, Habsburg agnatic succession rules]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: predecessorLawModified Context triple: [Pragmatic Sanction of 1713, predecessorLawModified, Habsburg agnatic succession rules]
-
A.
predecessor
Indicates that one entity comes before another in an ordered sequence or succession.
-
B.
precedentFor
Indicates that one situation, decision, or case serves as an authoritative example or basis for deciding or interpreting another.
-
C.
wasSupersededBy
Indicates that one entity has been replaced or made obsolete by another entity that takes over its role or function.
-
D.
amendedBy
Indicates that one entity has been modified, revised, or updated as a result of changes made by another entity.
-
E.
successor
Indicates that one entity directly follows another in an ordered sequence or position.
- 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_69a25374990081909766d30c79a18e0e |
completed | Feb. 28, 2026, 2:31 a.m. |
| NER | Named-entity recognition | batch_69a25a3f9d188190aacf5791273e2c65 |
completed | Feb. 28, 2026, 3 a.m. |
| PD | Predicate disambiguation | batch_69a25667717c8190bac5108366e2178d |
completed | Feb. 28, 2026, 2:43 a.m. |
| PDg | Predicate description generation | batch_69a25a3ee6d08190a451ddba7504ce9b |
completed | Feb. 28, 2026, 3 a.m. |
Created at: Feb. 28, 2026, 2:39 a.m.