Triple
T4393791
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Washington/Wells |
E99430
|
entity |
| Predicate | hasCustomerAssistanceBooth |
P31157
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Washington/Wells, hasCustomerAssistanceBooth, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCustomerAssistanceBooth Context triple: [Washington/Wells, hasCustomerAssistanceBooth, yes]
-
A.
hasCustomerAssistanceArea
chosen
Indicates that an entity includes or provides a designated area or facility for assisting customers.
-
B.
hasTranslationBooths
Indicates that one entity provides or contains translation booths for use, typically for interpreting spoken communication.
-
C.
hasCustomerServiceChannel
Indicates that an entity provides or is associated with a specific channel or medium through which customer service interactions can occur.
-
D.
hasServiceCenter
Indicates that an entity maintains or is associated with a service center that provides support, repair, or maintenance services.
-
E.
hasCollectorBooth
Indicates that an entity has an associated collector booth, typically a designated place or station where collection-related activities (such as payments, tickets, or items) are handled.
- 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_69b345506b408190b0e3dee616738a7d |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b352a8862481909dc67abf42be6928 |
completed | March 12, 2026, 11:56 p.m. |
| PD | Predicate disambiguation | batch_69b34f597998819092477efdedb51427 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:19 p.m.