Triple
T608503
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boston Harbor |
E12045
|
entity |
| Predicate | underwentCleanup |
P6390
|
FINISHED |
| Object | late 20th century |
—
|
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: late 20th century | Statement: [Boston Harbor, underwentCleanup, late 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: underwentCleanup Context triple: [Boston Harbor, underwentCleanup, late 20th century]
-
A.
underwent
chosen
Indicates that an entity experienced or was subjected to a process, event, or change, typically as the patient of an action.
-
B.
destroyedDuring
Indicates that one entity was destroyed in the course of, or as a consequence of, a specified event or time period.
-
C.
undergoing
Indicates that an entity is currently experiencing, being subjected to, or in the process of a particular action, change, or treatment.
-
D.
undertook
Indicates that an entity assumed responsibility for starting and carrying out a task, project, or action.
-
E.
killedDuring
Indicates that one entity caused the death of another entity in the course of, or as part of, a specified event or time period.
- 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_69a493309df48190a327f748e88049a6 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49df54eec8190af3f5f04c01d5d2a |
completed | March 1, 2026, 8:13 p.m. |
| PD | Predicate disambiguation | batch_69a49cf8fc1c81908a9c7df552aa1a59 |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:35 p.m.