Triple
T38078858
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Atlantic Ocean via Merrimack River |
E950795
|
entity |
| Predicate | hasEndpointLocation |
P196647
|
FINISHED |
| Object | Atlantic coast of 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: Atlantic coast of Massachusetts | Statement: [Atlantic Ocean via Merrimack River, hasEndpointLocation, Atlantic coast of Massachusetts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEndpointLocation Context triple: [Atlantic Ocean via Merrimack River, hasEndpointLocation, Atlantic coast of Massachusetts]
-
A.
hasPrimaryEndpoint
Indicates that an entity designates another entity as its main or most important endpoint or target location.
-
B.
hasEndpointCity
Indicates that a route, connection, or path terminates at a particular city as one of its endpoints.
-
C.
hasEndpointType
Indicates that an entity has a specific type or classification assigned to one of its endpoints.
-
D.
hasEndpointCountry
Indicates that an entity such as a route, connection, or infrastructure element terminates or has an endpoint located in a specified country.
-
E.
usesEndpoint
Indicates that one entity accesses or interacts with a specific endpoint to perform an operation or exchange data.
- F. None of above. chosen
Provenance (4 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_69f76f02a6c48190a94f3c0b3ee90cf2 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fe5ec9028081909ae3d6fbe2f4cbbc |
completed | May 8, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69fe5e1d715881909fc516fafc707644 |
completed | May 8, 2026, 10:05 p.m. |
| PDg | Predicate description generation | batch_69fe5ec84910819094cb15269ace7c51 |
completed | May 8, 2026, 10:08 p.m. |
Created at: May 3, 2026, 4:21 p.m.