Triple
T31897165
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Polish state |
E814314
|
entity |
| Predicate | dateOfFirstStateFormation |
P13772
|
FINISHED |
| Object | 10th century |
—
|
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: 10th century | Statement: [Polish state, dateOfFirstStateFormation, 10th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateOfFirstStateFormation Context triple: [Polish state, dateOfFirstStateFormation, 10th century]
-
A.
stateFounded
Indicates that a particular state was established or created at a specific time or by a specific founding event or agent.
-
B.
statehoodYear
Indicates the year in which an entity officially became a recognized state or attained statehood status.
-
C.
stateFoundedIn
chosen
Indicates that a particular state was established or came into existence in a specified year or time period.
-
D.
dateBecamePartOfUnitedStates
Indicates the date on which an entity formally became part of the United States.
-
E.
firstConstitutedIn
Indicates the time or context in which an entity (such as an organization, body, or structure) was originally formed or formally established.
- 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_69f348f04d7881909537fc9e7cbc670e |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fbc9d1dba881908c399b8e1dc13ce2 |
completed | May 6, 2026, 11:08 p.m. |
| PD | Predicate disambiguation | batch_69fbc8ec03ac8190a757563f96fab283 |
completed | May 6, 2026, 11:04 p.m. |
Created at: April 30, 2026, 11:59 p.m.