Triple
T10601880
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Freeland, Washington |
E275766
|
entity |
| Predicate | economicRoleOnIsland |
P8652
|
FINISHED |
| Object | commercial hub for South Whidbey |
—
|
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: commercial hub for South Whidbey | Statement: [Freeland, Washington, economicRoleOnIsland, commercial hub for South Whidbey]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: economicRoleOnIsland Context triple: [Freeland, Washington, economicRoleOnIsland, commercial hub for South Whidbey]
-
A.
roleAtSavoIsland
Indicates the specific role, position, or function an entity held in relation to the event or context associated with Savo Island.
-
B.
ethnicRole
Indicates a role, function, or social position that is specifically associated with or defined by an entity’s ethnicity.
-
C.
roleOfPeopleOnIt
Indicates the specific roles or functions that people have in relation to a particular object, event, or context.
-
D.
occupationOf
Indicates that one entity holds or performs the job, role, or profession associated with another entity.
-
E.
urbanRole
chosen
Indicates the function, status, or role that an entity holds within an urban or city context.
- 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_69d6aaf948d88190806cc3a8c47a3fb2 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d6df4992248190b640d743ccf02c82 |
completed | April 8, 2026, 11:05 p.m. |
| PD | Predicate disambiguation | batch_69d6dd72c1288190adbb5e79e94c044a |
completed | April 8, 2026, 10:57 p.m. |
Created at: April 8, 2026, 7:31 p.m.