Triple
T27784976
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rheinbundakte |
E700935
|
entity |
| Predicate | altersStatusOf |
P141118
|
FINISHED |
| Object | Bavaria |
—
|
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: Bavaria | Statement: [Rheinbundakte, altersStatusOf, Bavaria]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: altersStatusOf Context triple: [Rheinbundakte, altersStatusOf, Bavaria]
-
A.
statusChange
Indicates a transition in an entity’s state or condition from one status to another over time.
-
B.
actStatus
Indicates the current state or condition of an action or event, such as whether it is planned, ongoing, completed, or cancelled.
-
C.
legalStatusChangedIn
Indicates that an entity’s legal status was altered or reclassified within a specified jurisdiction, context, or time frame.
-
D.
alteredBy
chosen
Indicates that one entity has been changed, modified, or otherwise affected in form, state, or properties as a result of another entity’s action or influence.
-
E.
mayChangeTo
Indicates that one state, condition, or value is allowed or able to transition into another.
- 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_69ef6a50d8088190acbf3dfbb06d8091 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f6562fd3488190be1acd8c526a28d2 |
completed | May 2, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69f651a931748190a637e631a52bbfaa |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 27, 2026, 5:24 p.m.