Triple
T11423086
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Plymouth (Oregon) |
E270674
|
entity |
| Predicate | usedAsTownNameFor |
P99228
|
FINISHED |
| Object | riverfront settlement on the Columbia River |
—
|
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: riverfront settlement on the Columbia River | Statement: [Plymouth (Oregon), usedAsTownNameFor, riverfront settlement on the Columbia River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsTownNameFor Context triple: [Plymouth (Oregon), usedAsTownNameFor, riverfront settlement on the Columbia River]
-
A.
usedAsTownNameUntil
Indicates that an entity served as the official or common name of a town up to a specified point in time.
-
B.
usedAsTownNameInCentury
Indicates that a particular name was in use as the name of a town during a specified century.
-
C.
usedAsCountyNameUntil
Indicates that an entity served as the official name of a county up to a specified point in time.
-
D.
nicknameOfTown
Indicates that one entity is a nickname or informal name used to refer to a particular town.
-
E.
usedForCapitalOf
Indicates that something serves as the capital city or primary administrative center of a specified political or geographic entity.
- F. None of above. chosen
Provenance (4 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_69d6aadeef688190874bcecd88b3dd9b |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d801b357e88190ace56d36a945688f |
completed | April 9, 2026, 7:44 p.m. |
| PD | Predicate disambiguation | batch_69d7e71436f88190ac7e45a04ea5c987 |
completed | April 9, 2026, 5:51 p.m. |
| PDg | Predicate description generation | batch_69d80010712c819089ea2e31e664abe1 |
completed | April 9, 2026, 7:37 p.m. |
Created at: April 8, 2026, 9:34 p.m.