Triple
T25013796
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Fork |
E626070
|
entity |
| Predicate | majorTownsInclude |
P118397
|
FINISHED |
| Object | Southampton |
—
|
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: Southampton | Statement: [South Fork, majorTownsInclude, Southampton]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorTownsInclude Context triple: [South Fork, majorTownsInclude, Southampton]
-
A.
majorTownInRegion
chosen
Indicates that a town is one of the principal or most significant towns within a specified region.
-
B.
majorTownOnEdge
Indicates that a town is a principal or significant settlement located at or very near the boundary or perimeter of a specified area or feature.
-
C.
majorCityAlong
Indicates that a major city is located along the course or path of a specified geographic feature, such as a river, road, or route.
-
D.
nearestMajorTowns
Indicates that one or more major towns are the closest significant urban centers to a given location or entity.
-
E.
mainCities
Indicates that the related entities are the primary or most important cities associated with a given region, country, or area.
- 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_69e2ff27755881908490178e83701160 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f61f12b0f08190bc4a16907941864c |
completed | May 2, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69f61b37a5648190b10d33ae205ccfee |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 18, 2026, 6:06 a.m.