Triple
T12805997
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kuyavian Piasts |
E306144
|
entity |
| Predicate | roleInPoland |
P106480
|
FINISHED |
| Object | regional consolidation of Kuyavia |
—
|
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: regional consolidation of Kuyavia | Statement: [Kuyavian Piasts, roleInPoland, regional consolidation of Kuyavia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInPoland Context triple: [Kuyavian Piasts, roleInPoland, regional consolidation of Kuyavia]
-
A.
roleInEurope
Indicates that an entity holds a specific function, position, or responsibility within a European context, such as within Europe as a region or its institutions.
-
B.
objectivePoland
Indicates that something has Poland as its goal, target, or intended destination.
-
C.
ethnicRole
Indicates a role, function, or social position that is specifically associated with or defined by an entity’s ethnicity.
-
D.
roleInPakistan
Indicates that an entity holds or has held a specific role, position, or function within the context of Pakistan.
-
E.
roleInPhilippines
Indicates that an entity holds or has held an official or notable role, position, or function within the Philippines.
- 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_69d7bdf366888190a8cccb982606889c |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96e7f370c8190b3fc39c1b63394c6 |
completed | April 10, 2026, 9:41 p.m. |
| PD | Predicate disambiguation | batch_69d9640ed7448190b276e7fab649f7d2 |
completed | April 10, 2026, 8:56 p.m. |
| PDg | Predicate description generation | batch_69d96d88be0481908c311f1e71b61e70 |
completed | April 10, 2026, 9:37 p.m. |
Created at: April 9, 2026, 5:31 p.m.