Triple
T23322149
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Myersville, Maryland |
E591179
|
entity |
| Predicate | directionFromFrederickMaryland |
P151866
|
FINISHED |
| Object | west |
—
|
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: west | Statement: [Myersville, Maryland, directionFromFrederickMaryland, west]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: directionFromFrederickMaryland Context triple: [Myersville, Maryland, directionFromFrederickMaryland, west]
-
A.
directionFromBaltimore
Indicates the compass direction or relative bearing of one place or object when measured starting from Baltimore.
-
B.
directionFromWashingtonDC
Indicates the cardinal or relative compass direction of one place or object as measured from Washington, D.C.
-
C.
directionFromTrenton
Indicates the cardinal or relative compass direction in which one entity is located from Trenton.
-
D.
directionFromGreatFalls
Indicates the cardinal or relative compass direction of one entity as measured from the location of Great Falls.
-
E.
directionFromColumbus
Indicates the compass direction in which one location lies when measured from Columbus.
- 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_69e25d1effe4819096907f95f610dbff |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1978672148190bb90804361bb896b |
completed | April 29, 2026, 5:30 a.m. |
| PD | Predicate disambiguation | batch_69effcf8ca2c8190887d4f4656617d21 |
completed | April 28, 2026, 12:19 a.m. |
| PDg | Predicate description generation | batch_69f01d88b4ec8190a2a17a88e0eda178 |
completed | April 28, 2026, 2:38 a.m. |
Created at: April 17, 2026, 5:07 p.m.