Triple
T29903240
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | early Polish state |
E759467
|
entity |
| Predicate | hasFirstHistoricallyAttestedRuler |
P113819
|
FINISHED |
| Object | Mieszko I of Poland |
—
|
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: Mieszko I of Poland | Statement: [early Polish state, hasFirstHistoricallyAttestedRuler, Mieszko I of Poland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFirstHistoricallyAttestedRuler Context triple: [early Polish state, hasFirstHistoricallyAttestedRuler, Mieszko I of Poland]
-
A.
hasNumberOfRulers
Indicates the quantity of rulers associated with or governing a given entity.
-
B.
hasFamousRuler
Indicates that an entity is or was ruled by a ruler who is widely recognized or historically notable.
-
C.
hasFirstRuler
chosen
Indicates that an entity has another entity as its earliest or original ruler.
-
D.
hasFormerRuler
Indicates that an entity previously served as the ruler of another entity but no longer holds that ruling position.
-
E.
hasDynastyFounded
Indicates that an entity is the founder or originator of a particular dynasty.
- 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_69f224600590819085e148a01c056ef6 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69fdd5fba5048190b7d430ae2054a1fd |
completed | May 8, 2026, 12:24 p.m. |
| PD | Predicate disambiguation | batch_69fdd35f76f88190a1854ea27132f9c7 |
completed | May 8, 2026, 12:13 p.m. |
Created at: April 29, 2026, 6:07 p.m.