Triple
T31039637
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Suncook River |
E790952
|
entity |
| Predicate | courseChangeCause |
P6009
|
FINISHED |
| Object | flooding in May 2006 |
—
|
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 in May 2006 | Statement: [Suncook River, courseChangeCause, flooding in May 2006]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: courseChangeCause Context triple: [Suncook River, courseChangeCause, flooding in May 2006]
-
A.
disciplineChange
Indicates a change in an entity’s disciplinary status, such as adding, removing, or modifying a disciplinary action or category.
-
B.
changeReason
Indicates the reason or justification for a modification or change made to an entity or its state.
-
C.
reasonForChange
chosen
Indicates that one entity serves as the cause, justification, or motivation for a modification or change in another entity or state.
-
D.
courseSetting
Indicates the context or environment in which a course is delivered or conducted.
-
E.
courseDirectionChange
Indicates a change in the direction or path of movement of an entity from its previous course.
- 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_69f224ca2fa881908a3ac5fedf207b90 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f694f8cc988190b8e6e87a9d1f7d41 |
completed | May 3, 2026, 12:21 a.m. |
| PD | Predicate disambiguation | batch_69f690f13d7481908ddfefe95df2a1c2 |
completed | May 3, 2026, 12:04 a.m. |
Created at: April 29, 2026, 8:59 p.m.