Triple
T27784970
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rheinbundakte |
E700935
|
entity |
| Predicate | definesTypeOfState |
P56536
|
FINISHED |
| Object | Confederation of the Rhine as a confederation of states |
—
|
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: Confederation of the Rhine as a confederation of states | Statement: [Rheinbundakte, definesTypeOfState, Confederation of the Rhine as a confederation of states]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesTypeOfState Context triple: [Rheinbundakte, definesTypeOfState, Confederation of the Rhine as a confederation of states]
-
A.
typeOfState
Indicates that one state is a specific kind or category of another, more general state.
-
B.
definesType
chosen
Indicates that one entity specifies or establishes the type or classification of another entity.
-
C.
definitionType
Indicates the specific kind or category of definition that characterizes how one entity is defined in relation to another.
-
D.
definesStateName
Indicates that an entity specifies or assigns the official name of a state.
-
E.
typeOfStateBody
Indicates that one entity is a specific kind or category of state-level governing body relative to another entity.
- 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_69f760a35b988190904e6267553ad2fe |
completed | May 3, 2026, 2:50 p.m. |
| PD | Predicate disambiguation | batch_69f75eb3d6f081908c933474eb359e3d |
completed | May 3, 2026, 2:41 p.m. |
Created at: April 27, 2026, 5:24 p.m.