Triple
T37849598
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | George Washington Memorial Bridge |
E944004
|
entity |
| Predicate | hasHistoricPlaques |
P57238
|
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: [George Washington Memorial Bridge, hasHistoricPlaques, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHistoricPlaques Context triple: [George Washington Memorial Bridge, hasHistoricPlaques, yes]
-
A.
hasCommemorativePlaques
chosen
Indicates that one entity possesses or displays commemorative plaques associated with it.
-
B.
hasHistoricStreetscape
Indicates that an entity possesses or is characterized by a streetscape of recognized historical significance or heritage value.
-
C.
isHistoricPlace
Indicates that a place holds recognized historical significance, often due to its age, events, or cultural importance.
-
D.
hasHistoricSurroundings
Indicates that something is located within or closely associated with an area characterized by historically significant features, buildings, or context.
-
E.
hasHistoricDistrict
Indicates that an entity possesses or contains a designated historic district within its boundaries or domain.
- 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_69f76eed4d9c81908b1b71ba9e3b61fe |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69ffa5f31c8881908c26e2aa52df6ece |
completed | May 9, 2026, 9:24 p.m. |
| PD | Predicate disambiguation | batch_69ffa42aee408190ad1a5f285688b338 |
completed | May 9, 2026, 9:16 p.m. |
Created at: May 3, 2026, 4:19 p.m.