Triple
T14142751
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Usonian houses |
E350465
|
entity |
| Predicate | typicalSiteStrategy |
P112982
|
FINISHED |
| Object | sited on large natural lots |
—
|
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: sited on large natural lots | Statement: [Usonian houses, typicalSiteStrategy, sited on large natural lots]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalSiteStrategy Context triple: [Usonian houses, typicalSiteStrategy, sited on large natural lots]
-
A.
traditionalSite
Indicates that a site is recognized or used according to long-established customs, practices, or cultural traditions.
-
B.
typeOfSite
Indicates the specific category or kind of site that an entity is classified as.
-
C.
siteTypeServed
Indicates the type of site or location that is served, supported, or handled by a given entity or resource.
-
D.
isSiteSpecific
Indicates that something is designed, intended, or valid only for a particular location, context, or site and does not generally apply elsewhere.
-
E.
containsSite
Indicates that one entity spatially or structurally includes another entity as a site or location within its bounds.
- F. None of above. chosen
Provenance (4 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_69d827865f608190b311820428ae027b |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de611ed3508190add37baa30d1d134 |
completed | April 14, 2026, 3:45 p.m. |
| PD | Predicate disambiguation | batch_69de05b5e7a08190a16be9ad8b92b80c |
completed | April 14, 2026, 9:15 a.m. |
| PDg | Predicate description generation | batch_69de239a02e881909b0e2679487e4ab2 |
completed | April 14, 2026, 11:23 a.m. |
Created at: April 10, 2026, 12:51 a.m.