Triple
T31897164
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Polish state |
E814314
|
entity |
| Predicate | hasIndependenceTraditionFrom |
P200126
|
FINISHED |
| Object | early Middle Ages |
—
|
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: early Middle Ages | Statement: [Polish state, hasIndependenceTraditionFrom, early Middle Ages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIndependenceTraditionFrom Context triple: [Polish state, hasIndependenceTraditionFrom, early Middle Ages]
-
A.
hasIndependence
Indicates that an entity possesses or has achieved political, legal, or functional independence from another controlling authority.
-
B.
hasIndependenceStatus
Indicates the type or condition of an entity’s political or administrative independence.
-
C.
independenceCountry
Indicates that a country has achieved political independence, typically from a former governing or colonial power.
-
D.
independenceProclaimedAt
Indicates the specific time or date at which an entity formally declared its independence.
-
E.
hasPostIndependenceStatus
Indicates the status or condition an entity holds in the period after a country or region has gained independence.
- 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_69f348f04d7881909537fc9e7cbc670e |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69ff76ac40988190a34d858b5472ee2b |
completed | May 9, 2026, 6:02 p.m. |
| PD | Predicate disambiguation | batch_69ff760a90948190a12fcb80e6e3e14b |
completed | May 9, 2026, 5:59 p.m. |
| PDg | Predicate description generation | batch_69ff76ab9b4c8190b4cc7c9c733b2765 |
completed | May 9, 2026, 6:02 p.m. |
Created at: April 30, 2026, 11:59 p.m.