Triple
T33547305
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Musée Cognacq-Jay |
E859239
|
entity |
| Predicate | relocatedToHôtelDonon |
P1660
|
FINISHED |
| Object | 1990 |
—
|
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: 1990 | Statement: [Musée Cognacq-Jay, relocatedToHôtelDonon, 1990]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relocatedToHôtelDonon Context triple: [Musée Cognacq-Jay, relocatedToHôtelDonon, 1990]
-
A.
movedToVersaillesUnder
Indicates that one entity relocated to Versailles under the authority, rule, or auspices of another entity.
-
B.
oppositeTownAcrossRhône
Indicates that one town is located directly across the Rhône River from another town, on the opposite bank.
-
C.
relocatedTo
chosen
Indicates that an entity has moved or been transferred from its previous location to a new specified location.
-
D.
reservationLocatedIn
Indicates that a reservation (such as a booking or held resource) is situated within or associated with a specific location or place.
-
E.
reservationLocatedAlong
Indicates that a reservation is situated along, adjacent to, or following the course or extent of a specified linear feature such as a road, river, or boundary.
- 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_69f3497a5be08190a39b12736899e034 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6f70c17d88190aa74afc2dd2a0467 |
completed | May 3, 2026, 7:19 a.m. |
| PD | Predicate disambiguation | batch_69f6f6632dfc8190af85e258c8519207 |
completed | May 3, 2026, 7:16 a.m. |
Created at: May 1, 2026, 1:39 a.m.