Triple
T31266750
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pfister family |
E797273
|
entity |
| Predicate | hasNotableBuildingLocation |
P153329
|
FINISHED |
| Object | Colmar, Haut-Rhin |
—
|
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: Colmar, Haut-Rhin | Statement: [Pfister family, hasNotableBuildingLocation, Colmar, Haut-Rhin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableBuildingLocation Context triple: [Pfister family, hasNotableBuildingLocation, Colmar, Haut-Rhin]
-
A.
hasNotableGovernmentBuilding
Indicates that a location possesses a government building that is significant or prominent in some recognized way.
-
B.
containsNotablePlace
chosen
Indicates that one location includes within its boundaries a place that is considered notable or significant.
-
C.
hasBuildingLocation
Indicates that a building is situated at, or associated with, a specific geographic or spatial location.
-
D.
notableLocation
Indicates that a location is especially significant, prominent, or noteworthy in relation to the subject.
-
E.
emblematicBuildingLocation
Indicates that a building serves as a symbolic or representative landmark for a particular location or area.
- 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_69f224de2bbc819081af6c32e1d857b9 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a008c77d4dc8190b342d7407eaf48fa |
completed | May 10, 2026, 1:47 p.m. |
| PD | Predicate disambiguation | batch_6a008c18531c8190bbe883b73e6d023f |
completed | May 10, 2026, 1:46 p.m. |
Created at: April 29, 2026, 9:13 p.m.