Triple
T18824339
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hofwyl-Broadfield Plantation State Historic Site |
E460344
|
entity |
| Predicate | situatedInRegion |
P9687
|
FINISHED |
| Object | coastal Georgia |
—
|
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: coastal Georgia | Statement: [Hofwyl-Broadfield Plantation State Historic Site, situatedInRegion, coastal Georgia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: situatedInRegion Context triple: [Hofwyl-Broadfield Plantation State Historic Site, situatedInRegion, coastal Georgia]
-
A.
placeRegion
Indicates that a place is located within, or is part of, a larger geographic or administrative region.
-
B.
subregionOf
Indicates that one region is geographically or administratively contained within, and is a part of, another larger region.
-
C.
foundInRegion
chosen
Indicates that something is located within, occurs in, or is associated with a specific geographic or spatial region.
-
D.
region1
Indicates that one entity is the first or primary region associated with, containing, or encompassing another entity.
-
E.
isRegionOf
Indicates that one entity is a geographic or administrative region belonging to, contained within, or associated with another 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_69d8dcf94c288190a06dea029ae4b223 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5a6bce5588190bd0aefcd0c51edad |
completed | April 20, 2026, 4:08 a.m. |
| PD | Predicate disambiguation | batch_69e48d1b10ec8190985c6fb5766ff981 |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:56 a.m.