Triple
T14740606
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | d’Oultremont |
E346333
|
entity |
| Predicate | hasFamilyNameForm |
P27865
|
FINISHED |
| Object | Oultremont |
E1109450
|
NE 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: Oultremont | Statement: [d’Oultremont, hasFamilyNameForm, Oultremont]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Oultremont Context triple: [d’Oultremont, hasFamilyNameForm, Oultremont]
-
A.
Oultremont
chosen
Oultremont is a noble family name associated with the historic Belgian aristocratic House of Oultremont.
-
B.
Rejet-de-Beaulieu
Rejet-de-Beaulieu is a small commune in the Nord department of northern France, situated within the administrative area of Le Cateau-Cambrésis.
-
C.
Ville-au-Bois
Ville-au-Bois is a small settlement located within the municipality of Stoumont in the province of Liège, Belgium.
-
D.
Senneville
Senneville is a small, affluent suburban village located at the western tip of the Island of Montreal in Quebec, Canada.
-
E.
Marly-la-Ville
Marly-la-Ville is a commune in the Val-d'Oise department in the northern suburbs of Paris, France.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d822e6f1c88190bc494d491a907114 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69dec7345680819093e901233a064e48 |
completed | April 14, 2026, 11:01 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fdfb91fdf88190bdcc9a93289f6b7f |
completed | May 8, 2026, 3:04 p.m. |
Created at: April 10, 2026, 1:30 a.m.