Triple
T37694108
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charles River Bridge |
E938880
|
entity |
| Predicate | notableDecisionYear |
P2233
|
FINISHED |
| Object | 1837 |
—
|
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: 1837 | Statement: [Charles River Bridge, notableDecisionYear, 1837]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableDecisionYear Context triple: [Charles River Bridge, notableDecisionYear, 1837]
-
A.
notableSelectionYear
Indicates the year in which an entity was notably selected for a particular role, honor, list, or recognition.
-
B.
yearDecided
chosen
Indicates the specific calendar year in which a decision, ruling, or resolution was formally made or finalized.
-
C.
notableElectionYear
Indicates that a particular year is recognized as significant or noteworthy in the context of an election involving the given entity.
-
D.
notableDecisionArea
Indicates that a decision or choice is made in a particularly important, influential, or high-impact area or domain.
-
E.
notableWorkYear
Indicates the year in which a notable work associated with an entity was created, released, or achieved prominence.
- 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_69f76eda6ae48190b3111071eeacc038 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a1772e48190ba738c6d11b321e2 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:18 p.m.