Triple
T402844
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Versailles |
E9321
|
entity |
| Predicate | foundedAsCapitalOfCourt |
P5604
|
FINISHED |
| Object | 1682 |
—
|
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: 1682 | Statement: [Versailles, foundedAsCapitalOfCourt, 1682]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundedAsCapitalOfCourt Context triple: [Versailles, foundedAsCapitalOfCourt, 1682]
-
A.
wasFirstCapitalOf
Indicates that one place previously served as the earliest or original capital city of another political or administrative entity.
-
B.
formerCapitalOf
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.
capitalOfProvincePreviouslyLocatedOn
Indicates that an entity serves or served as the capital city of a province that was formerly situated in a specified location.
-
D.
inauguratedAsCapital
chosen
Indicates that a place was officially declared and established as the capital of a political or administrative entity.
-
E.
placeFounded
Indicates the location where an entity (such as an organization or institution) was originally established or founded.
- 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_69a2e8004cb88190b92ed1add6abf41a |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2eca0e2048190a7bf360257965e56 |
completed | Feb. 28, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_69a2e96ee4ec8190a5c0e3f491d3963d |
completed | Feb. 28, 2026, 1:11 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.