Triple
T33063499
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reynolds Lake Oconee |
E846033
|
entity |
| Predicate | hasTypeOfRealEstate |
P5777
|
FINISHED |
| Object | primary residences |
—
|
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: primary residences | Statement: [Reynolds Lake Oconee, hasTypeOfRealEstate, primary residences]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeOfRealEstate Context triple: [Reynolds Lake Oconee, hasTypeOfRealEstate, primary residences]
-
A.
typeOfHouse
Indicates the specific category or kind of house associated with an entity (e.g., apartment, detached house, townhouse).
-
B.
hasEstateType
Indicates that an entity possesses or is associated with a particular category or type of estate.
-
C.
propertyTypeOwned
Indicates that one entity owns a specific type or category of property in relation to another entity.
-
D.
realEstateCategory
chosen
Indicates the classification of a property into a specific type or category within real estate (e.g., residential, commercial, industrial).
-
E.
propertyType_id
Indicates a relationship that specifies the type or category of a property associated with an 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_69f3495333b8819095e9af56855b9061 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fef2db323c8190821bda53f22a42be |
completed | May 9, 2026, 8:39 a.m. |
| PD | Predicate disambiguation | batch_69fef21d63c88190abf6a99b59b3c655 |
completed | May 9, 2026, 8:36 a.m. |
Created at: May 1, 2026, 1:25 a.m.