Triple
T38449286
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SR 144 |
E912124
|
entity |
| Predicate | isConnectorRouteOn |
P125679
|
FINISHED |
| Object | Westport Island, Maine |
—
|
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: Westport Island, Maine | Statement: [SR 144, isConnectorRouteOn, Westport Island, Maine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isConnectorRouteOn Context triple: [SR 144, isConnectorRouteOn, Westport Island, Maine]
-
A.
isRouteOn
chosen
Indicates that one route is located on, follows along, or is aligned with another specified path or infrastructure.
-
B.
isScenicConnectorBetween
Indicates that something serves as a visually appealing route or link connecting two locations or entities.
-
C.
hasConnector
Indicates that one entity is linked or joined to another entity through a connector or connecting element.
-
D.
isStandardRouteOn
Indicates that a particular route is the default or officially designated path used on a given transportation line or service.
-
E.
isRouteFor
Indicates that one entity serves as a path, course, or channel used for traveling, transporting, or connecting 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_69f76e84e2dc81908badf05b3aafa9ea |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fcdaa36f90819093f8661969990c7d |
completed | May 7, 2026, 6:32 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fefc588190b063d7ea1ec87b07 |
completed | May 7, 2026, 6:25 p.m. |
Created at: May 3, 2026, 4:31 p.m.