Triple
T15435625
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roberto Clemente Bridge |
E369753
|
entity |
| Predicate | riverBankOne |
P118771
|
FINISHED |
| Object | Downtown riverfront |
—
|
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: Downtown riverfront | Statement: [Roberto Clemente Bridge, riverBankOne, Downtown riverfront]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: riverBankOne Context triple: [Roberto Clemente Bridge, riverBankOne, Downtown riverfront]
-
A.
riverBankArea
Indicates the area of land adjacent to a riverbank associated with the given entity or location.
-
B.
riverBankOnSouthSide
Indicates that a river bank is located on the southern side of a specified river or watercourse.
-
C.
bank
Indicates that an entity provides financial services such as holding deposits, lending money, or managing financial transactions for another entity.
-
D.
riverBankOnEastSide
Indicates that a river bank is located on the eastern side of a river or watercourse.
-
E.
hasBank
Indicates that one entity possesses, is associated with, or is served by a particular bank (such as a financial institution or river bank).
- 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_69d85a19180081909925012fbf4e62a3 |
completed | April 10, 2026, 2:02 a.m. |
| NER | Named-entity recognition | batch_69e03edb3ec481908b26164d4470c9bc |
completed | April 16, 2026, 1:43 a.m. |
| PD | Predicate disambiguation | batch_69ded27f45548190a6d2b1b85cb47444 |
completed | April 14, 2026, 11:49 p.m. |
| PDg | Predicate description generation | batch_69ded57005608190886cd01f640dfedb |
completed | April 15, 2026, 12:01 a.m. |
Created at: April 10, 2026, 3:21 a.m.