Triple
T7297338
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mill Brook (Arlington, Massachusetts) |
E164556
|
entity |
| Predicate | watercourseIn |
P69640
|
FINISHED |
| Object | Arlington, Massachusetts |
—
|
NE NERFINISHED |
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: Arlington, Massachusetts | Statement: [Mill Brook (Arlington, Massachusetts), watercourseIn, Arlington, Massachusetts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: watercourseIn Context triple: [Mill Brook (Arlington, Massachusetts), watercourseIn, Arlington, Massachusetts]
-
A.
watercourseName
Indicates the name assigned to a river, stream, or other flowing body of water in the relationship.
-
B.
watercourseThroughRegion
chosen
Indicates that a watercourse (such as a river or stream) passes through or traverses a specified region.
-
C.
inflowWatercourse
Indicates that one watercourse flows into or feeds another water body or watercourse.
-
D.
watercourseId
Indicates the identifier that uniquely associates an entity with a specific watercourse (such as a river, stream, or canal).
-
E.
sourceOfWatercourse
Indicates that one entity is the origin or starting point from which a watercourse (such as a river or stream) begins or flows.
- 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_69c6887a499881909dd23341399c59d8 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6eb8e48d48190ada4d507f3b61bc4 |
completed | March 27, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69c6e76e67d88190bd3ca6864f45845a |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 3 p.m.