Triple
T14328602
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Copmanhurst |
E355278
|
entity |
| Predicate | geographicDirectionFromGrafton |
P113992
|
FINISHED |
| Object | inland |
—
|
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: inland | Statement: [Copmanhurst, geographicDirectionFromGrafton, inland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: geographicDirectionFromGrafton Context triple: [Copmanhurst, geographicDirectionFromGrafton, inland]
-
A.
directionFromAtlanta
Indicates the cardinal or relative compass direction in which one entity is located from Atlanta.
-
B.
directionFromColumbus
Indicates the compass direction in which one location lies when measured from Columbus.
-
C.
geographicDirectionWithinState
Indicates that one location lies in a specified cardinal or relative geographic direction within the boundaries of a particular state.
-
D.
geographicDirectionImpliedByName
Indicates that the name of a place or feature suggests a specific geographic direction (e.g., north, south, east, west) relative to some reference.
-
E.
geographicDirectionWithinBraintree
Indicates the relative geographic direction of one location with respect to another, specifically within the area of Braintree.
- 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_69d8278fa2108190bc0d0e7939c1eb03 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de8c1c3e70819084b6728ac5c18561 |
completed | April 14, 2026, 6:49 p.m. |
| PD | Predicate disambiguation | batch_69de2a9515f4819081aabf251bca5878 |
completed | April 14, 2026, 11:52 a.m. |
| PDg | Predicate description generation | batch_69de2e9ded24819099200349cf80e068 |
completed | April 14, 2026, 12:10 p.m. |
Created at: April 10, 2026, 1:13 a.m.