Triple
T34026373
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Cherry Blossom Festival Parade |
E872515
|
entity |
| Predicate | routeEndArea |
P21868
|
FINISHED |
| Object | near the Washington Monument |
—
|
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: near the Washington Monument | Statement: [National Cherry Blossom Festival Parade, routeEndArea, near the Washington Monument]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: routeEndArea Context triple: [National Cherry Blossom Festival Parade, routeEndArea, near the Washington Monument]
-
A.
routeEndRegion
chosen
Indicates the geographic region where a route terminates or reaches its endpoint.
-
B.
routeArea
Indicates that an area is associated with, covered by, or traversed by a particular route.
-
C.
routeCompleted
Indicates that a specified route has been fully traversed or finished by the relevant entity or process.
-
D.
roadAccessArea
Indicates that an area is designated for or provides access to a road, such as for entry, exit, or connection.
-
E.
startFinishArea
Indicates a relationship where a defined area serves as both the starting point and the finishing point for an event, route, or activity.
- 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_69f349a2527c81909a7cd4bda94d70ad |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f70fb4f18c819099ef6d9177b7d205 |
completed | May 3, 2026, 9:04 a.m. |
| PD | Predicate disambiguation | batch_69f70f3a54d481909ba6bdda3647b761 |
completed | May 3, 2026, 9:02 a.m. |
Created at: May 1, 2026, 1:51 a.m.