Triple
T27761497
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Main River valley |
E701481
|
entity |
| Predicate | majorTownAlong |
P107550
|
FINISHED |
| Object | Miltenberg |
—
|
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: Miltenberg | Statement: [Main River valley, majorTownAlong, Miltenberg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorTownAlong Context triple: [Main River valley, majorTownAlong, Miltenberg]
-
A.
majorCityAlong
chosen
Indicates that a major city is located along the course or path of a specified geographic feature, such as a river, road, or route.
-
B.
majorTownInRegion
Indicates that a town is one of the principal or most significant towns within a specified region.
-
C.
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.
-
D.
mainTownOn
Indicates that one town is the primary or principal town located on or associated with a particular geographic feature, route, or area.
-
E.
primaryTown
Indicates that a given town is the main or most important town associated with an entity (such as a person, organization, or region).
- 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_69ef6a5193808190816eb7d0020b2d87 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69fcdf2394748190b35cead3e208447d |
completed | May 7, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe344ec8190a0471911952f4b82 |
completed | May 7, 2026, 6:37 p.m. |
Created at: April 27, 2026, 4:27 p.m.