Triple
T29207161
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jacques Cœur |
E740443
|
entity |
| Predicate | palaceLocatedIn |
P166426
|
FINISHED |
| Object | Bourges |
—
|
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: Bourges | Statement: [Jacques Cœur, palaceLocatedIn, Bourges]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: palaceLocatedIn Context triple: [Jacques Cœur, palaceLocatedIn, Bourges]
-
A.
palace
Indicates that an entity is a palace, i.e., a grand official residence typically used by royalty or high-ranking authorities.
-
B.
seatOfPowerLocatedIn
Indicates that the primary governing authority or central power base of an entity is situated within a specified location.
-
C.
hasMunicipalPalaceIn
Indicates that a municipality possesses or is associated with a municipal palace located in the specified place.
-
D.
servedRoyalResidence
Indicates that an entity functioned as an official residence used by royalty.
-
E.
servedAsImperialResidenceFrom
Indicates that an entity functioned as an imperial residence starting from a specified point in time.
- F. None of above. chosen
Provenance (4 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_69f07cb974108190b7e86ca489a6ebb6 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f664022f0881908c77482eeead99d2 |
completed | May 2, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69f65c24f8b48190af81b575f3c15be5 |
completed | May 2, 2026, 8:18 p.m. |
| PDg | Predicate description generation | batch_69f65fb2ead08190b06677d4d6ea1ea8 |
completed | May 2, 2026, 8:33 p.m. |
Created at: April 28, 2026, 12:09 p.m.