Triple
T24696661
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saint-Bris family |
E611608
|
entity |
| Predicate | notablePropertyLocation |
P164759
|
FINISHED |
| Object | Amboise, Indre-et-Loire, France |
—
|
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: Amboise, Indre-et-Loire, France | Statement: [Saint-Bris family, notablePropertyLocation, Amboise, Indre-et-Loire, France]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notablePropertyLocation Context triple: [Saint-Bris family, notablePropertyLocation, Amboise, Indre-et-Loire, France]
-
A.
notableLocation
Indicates that a location is especially significant, prominent, or noteworthy in relation to the subject.
-
B.
notableCollectionLocation
Indicates the place where a notable collection of items, works, or artifacts is held or housed.
-
C.
notableShowLocation
Indicates that a show or performance is notably associated with, took place at, or is best known for occurring in a particular location.
-
D.
notablePlace
Indicates that a place is especially significant, famous, or noteworthy in relation to the subject.
-
E.
notablePropertyCluster
Indicates that multiple notable properties are grouped together as a coherent cluster or set associated with an entity.
- 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_69e2c4d76d148190b58ad612467149a5 |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f650fc44e48190bc0e0a935eac62a6 |
completed | May 2, 2026, 7:31 p.m. |
| PD | Predicate disambiguation | batch_69f64cab1f648190a2a9460690d18a37 |
completed | May 2, 2026, 7:12 p.m. |
| PDg | Predicate description generation | batch_69f650c466b881908954e43bfebae8a4 |
completed | May 2, 2026, 7:30 p.m. |
Created at: April 18, 2026, 3:22 a.m.