Triple
T17208199
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tugendhat family |
E417654
|
entity |
| Predicate | villaFunctionOriginally |
P31237
|
FINISHED |
| Object | private residence |
—
|
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: private residence | Statement: [Tugendhat family, villaFunctionOriginally, private residence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: villaFunctionOriginally Context triple: [Tugendhat family, villaFunctionOriginally, private residence]
-
A.
villaAlternativeName
Indicates that a villa is known by an alternative or additional name.
-
B.
houseFunction
chosen
Indicates the functional role or primary use that a house serves (e.g., residential, commercial, mixed-use).
-
C.
constructedAsVillaFor
Indicates that something was built or developed specifically to serve as a villa for a particular beneficiary or owner.
-
D.
villaCurrentOwner
Indicates the entity that is the present legal owner of a given villa.
-
E.
housesFacility
Indicates that one entity serves as a location or container in which the other entity (a facility) is situated or operates.
- 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_69d886d779488190b131369541c04e7d |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42dc283648190b2c1f957940024aa |
completed | April 19, 2026, 1:20 a.m. |
| PD | Predicate disambiguation | batch_69e3831e354881908c5505ffd15c84e9 |
completed | April 18, 2026, 1:11 p.m. |
Created at: April 10, 2026, 5:38 a.m.