Triple
T29967142
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wicomico Church, Virginia |
E761215
|
entity |
| Predicate | isInlandOrCoastalRegion |
P156876
|
FINISHED |
| Object | coastal region of Virginia |
—
|
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 region of Virginia | Statement: [Wicomico Church, Virginia, isInlandOrCoastalRegion, coastal region of Virginia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInlandOrCoastalRegion Context triple: [Wicomico Church, Virginia, isInlandOrCoastalRegion, coastal region of Virginia]
-
A.
isInCoastalRegion
chosen
Indicates that a location or area is situated within a coastal region, typically near or along a sea or ocean shoreline.
-
B.
isCoastalRegion
Indicates that a region is located along or directly adjacent to a sea or ocean coastline.
-
C.
isCoastalArea
Indicates that a given area is located along or directly adjacent to a sea or ocean coastline.
-
D.
isInlandFrom
Indicates that one place lies away from the coast, further toward the interior of the land, relative to another place.
-
E.
hasCoastalRegion
Indicates that a place possesses at least one region that borders or is directly adjacent to a sea or ocean.
- 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_69f22467626081908d5afea489590e96 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6786bd7208190b8bb4aa26506f597 |
completed | May 2, 2026, 10:19 p.m. |
| PD | Predicate disambiguation | batch_69f66ec8298c8190b41fe9d182c05676 |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 29, 2026, 6:30 p.m.