Triple
T31231143
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pennsylvania Route 16 |
E796283
|
entity |
| Predicate | generalDirectionFromMarylandLine |
P171050
|
FINISHED |
| Object | northeast |
—
|
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: northeast | Statement: [Pennsylvania Route 16, generalDirectionFromMarylandLine, northeast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: generalDirectionFromMarylandLine Context triple: [Pennsylvania Route 16, generalDirectionFromMarylandLine, northeast]
-
A.
directionFromFrederickMaryland
Indicates the spatial direction or bearing of an entity as measured from Frederick, Maryland.
-
B.
directionFromBaltimore
Indicates the compass direction or relative bearing of one place or object when measured starting from Baltimore.
-
C.
directionFromWashingtonDC
Indicates the cardinal or relative compass direction of one place or object as measured from Washington, D.C.
-
D.
directionFromTrenton
Indicates the cardinal or relative compass direction in which one entity is located from Trenton.
-
E.
mainStraightDirection
Indicates the direction in which the primary or central straight path or segment is oriented or extends.
- 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_69f224da98f88190ab32f690cce5d303 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69c6d50c08190b7011e9904e55922 |
completed | May 3, 2026, 12:53 a.m. |
| PD | Predicate disambiguation | batch_69f696673214819094350e1d2648ef34 |
completed | May 3, 2026, 12:27 a.m. |
| PDg | Predicate description generation | batch_69f6978ec27c8190a488e1f9c2566d38 |
completed | May 3, 2026, 12:32 a.m. |
Created at: April 29, 2026, 9:10 p.m.