Triple
T34545213
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Poienari Fortress |
E886905
|
entity |
| Predicate | governedDuringMedievalPeriodBy |
P73014
|
FINISHED |
| Object | Princes of Wallachia |
—
|
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: Princes of Wallachia | Statement: [Poienari Fortress, governedDuringMedievalPeriodBy, Princes of Wallachia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governedDuringMedievalPeriodBy Context triple: [Poienari Fortress, governedDuringMedievalPeriodBy, Princes of Wallachia]
-
A.
governedInAntiquityBy
Indicates that one entity exercised political rule or authority over another entity during ancient or classical historical periods.
-
B.
medievalState
Indicates that an entity functioned as a state or political unit during the medieval historical period.
-
C.
eraOfHistoricalKingdom
Indicates the historical time period during which a particular kingdom existed or held prominence.
-
D.
historicallyUnderRuleOf
chosen
Indicates that one entity was historically governed, controlled, or ruled by another entity during a past period.
-
E.
governingEmpire
Indicates that one entity serves as the ruling imperial power that controls or governs another entity.
- 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_69f349ce5eb881909e431c670944aa68 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a013c50bcb8819086d163f1a796a9b8 |
completed | May 11, 2026, 2:17 a.m. |
| PD | Predicate disambiguation | batch_6a013c01bac88190b15c70910c02a8a7 |
completed | May 11, 2026, 2:16 a.m. |
Created at: May 1, 2026, 2:02 a.m.