Triple
T35725753
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blaine School District |
E1032606
|
entity |
| Predicate | servesExclave |
P201834
|
FINISHED |
| Object | Point Roberts, Washington |
—
|
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: Point Roberts, Washington | Statement: [Blaine School District, servesExclave, Point Roberts, Washington]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesExclave Context triple: [Blaine School District, servesExclave, Point Roberts, Washington]
-
A.
servesAgency
Indicates that one entity performs services or functions on behalf of, or under the authority of, an agency.
-
B.
servedSystem
Indicates that one system has provided service, functionality, or resources to another system.
-
C.
servesFeature
Indicates that one entity provides or makes available a particular feature or functionality to another entity.
-
D.
servesUnder
Indicates that one entity works in a subordinate role under the authority, command, or supervision of another entity.
-
E.
servesAsGatewayTo
Indicates that one entity functions as an entry point, access route, or intermediary channel that enables reaching or connecting to another 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_69f76e102b5881909e5d63a30a5cecbe |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a0027e4a59481909417b2531daaf480 |
completed | May 10, 2026, 6:38 a.m. |
| PD | Predicate disambiguation | batch_6a0026a42bc08190ad3322ce625a523a |
completed | May 10, 2026, 6:33 a.m. |
| PDg | Predicate description generation | batch_6a0027e384d08190ad92a6a21c8f84b5 |
completed | May 10, 2026, 6:38 a.m. |
Created at: May 3, 2026, 4:05 p.m.