Triple
T19621792
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South County |
E471025
|
entity |
| Predicate | popularNameFor |
P22212
|
FINISHED |
| Object | coastal region of Washington County, Rhode Island |
—
|
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 Washington County, Rhode Island | Statement: [South County, popularNameFor, coastal region of Washington County, Rhode Island]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: popularNameFor Context triple: [South County, popularNameFor, coastal region of Washington County, Rhode Island]
-
A.
popularName
chosen
Indicates that the object is a commonly used or widely recognized name or nickname for the subject.
-
B.
nicknamedFor
Indicates that one entity serves as the source, inspiration, or reason for another entity’s nickname.
-
C.
givenNameFor
Indicates that one entity is the personal first name assigned to or used for another entity.
-
D.
nameOf
Indicates that one entity is the name or designation of another entity.
-
E.
namedForKnownFor
Indicates that one entity is named after another entity specifically because that other entity is notable or recognized for something.
- 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_69d8e510fa248190b7afb274a1d4cf73 |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e640e668408190bc1e12a336b0687b |
completed | April 20, 2026, 3:06 p.m. |
| PD | Predicate disambiguation | batch_69e514e5cb108190ae260e466c447314 |
completed | April 19, 2026, 5:46 p.m. |
Created at: April 10, 2026, 1:44 p.m.