Triple
T24240765
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crown Prince of Austria |
E603215
|
entity |
| Predicate | linkedHouseLaw |
P155311
|
FINISHED |
| Object | Pragmatic Sanction of 1713 |
—
|
NE NERFINISHED |
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: Pragmatic Sanction of 1713 | Statement: [Crown Prince of Austria, linkedHouseLaw, Pragmatic Sanction of 1713]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: linkedHouseLaw Context triple: [Crown Prince of Austria, linkedHouseLaw, Pragmatic Sanction of 1713]
-
A.
linkedLaw
Indicates that there is a connection or reference between an entity and a specific law or legal provision.
-
B.
estateLinkedToTitle
Indicates that a particular estate is legally or formally associated with a specific title.
-
C.
associatedHouse
Indicates a relationship where one entity is linked or connected to a particular house, typically as its related or corresponding house.
-
D.
relationshipBetweenHouses
Indicates a relational connection or association that exists between two or more houses.
-
E.
houseInvolved
Indicates that a house plays a significant role or is directly implicated in the specified event, situation, or relationship.
- 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_69e2953f631c819097cbb421046bd417 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f28a9f812c81909dba8fbb54d8985c |
completed | April 29, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69f1c448abec8190b87cbf9ed419a309 |
completed | April 29, 2026, 8:41 a.m. |
| PDg | Predicate description generation | batch_69f1c6d4e99081909f61899eccafb73e |
completed | April 29, 2026, 8:52 a.m. |
Created at: April 18, 2026, 12:03 a.m.