Triple
T25881056
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Unification of Germany |
E652050
|
entity |
| Predicate | mainDrivingState |
P159835
|
FINISHED |
| Object | Kingdom of Prussia |
—
|
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: Kingdom of Prussia | Statement: [Unification of Germany, mainDrivingState, Kingdom of Prussia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainDrivingState Context triple: [Unification of Germany, mainDrivingState, Kingdom of Prussia]
-
A.
drivingFocus
Indicates that one entity serves as the primary motivating force, priority, or central concern guiding another entity’s actions or decisions.
-
B.
driverStatus
Indicates the current operational or availability state of a driver in relation to their driving duties.
-
C.
isDriven
Indicates that one entity operates or controls the movement of another entity, typically a vehicle or device.
-
D.
drivesOn
Indicates that an entity uses or travels along a particular route, surface, or roadway as its path of movement.
-
E.
drivingPrinciple
Indicates that one entity functions as the core motivating idea, value, or rule that fundamentally guides or directs another entity’s behavior, decisions, or development.
- 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_69e7ab3b92cc81908febd90317862647 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6033e7ea4819097fd0c5f651b7a40 |
completed | May 2, 2026, 1:59 p.m. |
| PD | Predicate disambiguation | batch_69f5afec3e94819080d9ba86cf8c866e |
completed | May 2, 2026, 8:03 a.m. |
| PDg | Predicate description generation | batch_69f5f6b32a8881909baa0db57b80d56a |
completed | May 2, 2026, 1:05 p.m. |
Created at: April 22, 2026, 8:16 a.m.