Triple
T16736220
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Suceava |
E406724
|
entity |
| Predicate | historicalCapitalFrom |
P3417
|
FINISHED |
| Object | late 14th 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: late 14th century | Statement: [Suceava, historicalCapitalFrom, late 14th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalCapitalFrom Context triple: [Suceava, historicalCapitalFrom, late 14th century]
-
A.
historicalCapitalNow
Indicates that a location currently serves as the capital of an entity for which it also held capital status at some point in the past.
-
B.
formerCapitalOf
chosen
Indicates that a place once served as the capital of another entity (such as a country or region) but no longer holds that status.
-
C.
capitalOfRuledEntity
Indicates that a city or settlement serves as the capital of a political entity that rules or governs another entity.
-
D.
countryCapitalSince
Indicates that a specified city has served as the capital of a given country starting from a particular point in time.
-
E.
modernCapitalLocatedIn
Indicates that a present-day capital city is geographically situated within a specified region, country, or administrative 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_69d8838ffb088190a0b11149929006bf |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e39c3a86848190a03f243dd1bdb899 |
completed | April 18, 2026, 2:59 p.m. |
| PD | Predicate disambiguation | batch_69e319c807788190901250ab6e0ca55f |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:20 a.m.