Triple
T27714986
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clymer, Pennsylvania |
E698791
|
entity |
| Predicate | hasSettlementCountry |
P35311
|
FINISHED |
| Object | United States |
—
|
NE NERFINISHED |
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: United States | Statement: [Clymer, Pennsylvania, hasSettlementCountry, United States]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSettlementCountry Context triple: [Clymer, Pennsylvania, hasSettlementCountry, United States]
-
A.
settlementCountryRegion
chosen
Indicates the country or broader geographic region in which a settlement is located or administered.
-
B.
typicalSettlementCountry
Indicates the country in which an entity’s financial transactions, obligations, or trades are most commonly settled.
-
C.
isSetInCountry
Indicates that something (such as an event, story, or scene) takes place within the geographical or political boundaries of a specified country.
-
D.
hasSettlementOnUSSide
Indicates that a settlement is located on the United States side of a border or boundary.
-
E.
hasSettlementCurrency
Indicates that a financial transaction, contract, or account is settled using a specified currency.
- 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_69ef590f655c81909f93893b3b3219b2 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69fcf825ca7081909d06b0df33eb33f9 |
completed | May 7, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69fcf42160f0819096812a8bf590875e |
completed | May 7, 2026, 8:20 p.m. |
Created at: April 27, 2026, 3:04 p.m.