Triple
T21702469
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alewife neighborhood of Cambridge |
E535691
|
entity |
| Predicate | subjectToIssue |
P29037
|
FINISHED |
| Object | flooding risk |
—
|
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: flooding risk | Statement: [Alewife neighborhood of Cambridge, subjectToIssue, flooding risk]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subjectToIssue Context triple: [Alewife neighborhood of Cambridge, subjectToIssue, flooding risk]
-
A.
involvesIssue
chosen
Indicates that an action, event, or entity is related to, concerns, or includes a particular issue.
-
B.
disputeIssue
Indicates that there is a disagreement or conflict specifically concerning a particular issue or point of contention.
-
C.
statusIssue
Indicates that an entity has a problem, defect, or irregular condition affecting its normal or expected status.
-
D.
containsIssue
Indicates that one entity includes, encompasses, or has within it a particular issue, problem, or defect.
-
E.
hasIssueWith
Indicates that one entity experiences a problem, conflict, or concern related to another entity.
- 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_69e0c46b44c0819088ab883ebd44e0e8 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef9b8161348190842c433531cfaa5b |
completed | April 27, 2026, 5:23 p.m. |
| PD | Predicate disambiguation | batch_69e6969113cc8190ab69855ef5667e4b |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:45 p.m.