Triple
T32586400
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Westside MAX project |
E832933
|
entity |
| Predicate | extendedServiceTo |
P46757
|
FINISHED |
| Object | Beaverton, Oregon |
E36936
|
NE 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: Beaverton, Oregon | Statement: [Westside MAX project, extendedServiceTo, Beaverton, Oregon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: extendedServiceTo Context triple: [Westside MAX project, extendedServiceTo, Beaverton, Oregon]
-
A.
serviceExtendedTo
chosen
Indicates that a service has been made available or expanded to include a particular entity, location, or group.
-
B.
extendedFor
Indicates that something has been lengthened in duration, scope, or extent specifically for the benefit or use of another entity.
-
C.
extendedAuthorityTo
Indicates that one entity has granted or delegated its decision-making power or control to another entity.
-
D.
extendedIndefinitelyOn
Indicates that something was prolonged or continued without a specified end point in relation to something else.
-
E.
extendedIn
Indicates that one entity continues, prolongs, or expands the scope, duration, or range of another entity.
- F. None of above.
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_69f34929ff648190aded9424aa7564ae |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c66df4f48190b118f51553cd8437 |
completed | May 3, 2026, 3:52 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a347ba8c47481908eac2a95efef46bb |
completed | June 18, 2026, 11:13 p.m. |
| PD | Predicate disambiguation | batch_69f6bd2c138481908afa3ee3e91f8900 |
completed | May 3, 2026, 3:12 a.m. |
Created at: May 1, 2026, 1:04 a.m.