Triple
T28833514
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beit Furik |
E728114
|
entity |
| Predicate | hasTraditionalHousingStyle |
P108429
|
FINISHED |
| Object | stone houses |
—
|
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: stone houses | Statement: [Beit Furik, hasTraditionalHousingStyle, stone houses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTraditionalHousingStyle Context triple: [Beit Furik, hasTraditionalHousingStyle, stone houses]
-
A.
hasTraditionalHouseStyle
chosen
Indicates that an entity possesses or is characterized by a traditional style of house or residential architecture.
-
B.
traditionallyHouses
Indicates that one entity has historically or customarily served as the location or container for another entity.
-
C.
hasTraditionalFarmBuildings
Indicates that an entity possesses or includes buildings typically associated with traditional farming activities.
-
D.
associatedHouseStyle
Indicates a relationship where a house or building is linked to a particular architectural style or design tradition.
-
E.
traditionallyBuiltOver
Indicates that one entity has been constructed on top of another in a manner consistent with long-established or customary building practices.
- 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_69f0319dc6088190bbfaa206d40ed74a |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69fd7fdafbe881908a31fcb407af2c34 |
completed | May 8, 2026, 6:16 a.m. |
| PD | Predicate disambiguation | batch_69fd7ef0ea908190b5d83f71565bdb1c |
completed | May 8, 2026, 6:13 a.m. |
Created at: April 28, 2026, 6:38 a.m.