Triple
T12087145
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maison des Ducs de Brabant |
E287834
|
entity |
| Predicate | locatedOnSideOfGrandPlace |
P31095
|
FINISHED |
| Object | eastern side |
—
|
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: eastern side | Statement: [Maison des Ducs de Brabant, locatedOnSideOfGrandPlace, eastern side]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedOnSideOfGrandPlace Context triple: [Maison des Ducs de Brabant, locatedOnSideOfGrandPlace, eastern side]
-
A.
situatedOnSideOf
chosen
Indicates that one entity is located along or beside the lateral part or edge of another entity.
-
B.
situatedInQuarter
Indicates that one entity is located within or belongs to a specific quarter or district of a larger area.
-
C.
situatedNextTo
Indicates that one entity is located immediately beside another, with no significant separation between them.
-
D.
locationSide
Indicates that one entity is positioned on a particular side (e.g., left, right, front, back) relative to another entity or reference point.
-
E.
isLocatedOn
Indicates that one entity exists at or is situated upon the surface or area of another entity.
- 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_69d6ab4964708190850585628b287b0c |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9178ad99c8190a54777b9bbe998bc |
completed | April 10, 2026, 3:30 p.m. |
| PD | Predicate disambiguation | batch_69d915000454819089fee00022055599 |
completed | April 10, 2026, 3:19 p.m. |
Created at: April 8, 2026, 9:48 p.m.