Triple
T31033152
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wenlock Epoch |
E790783
|
entity |
| Predicate | upperGSSPLocation |
P125707
|
FINISHED |
| Object | Přídolí, Czech Republic |
—
|
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: Přídolí, Czech Republic | Statement: [Wenlock Epoch, upperGSSPLocation, Přídolí, Czech Republic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: upperGSSPLocation Context triple: [Wenlock Epoch, upperGSSPLocation, Přídolí, Czech Republic]
-
A.
lowerGSSPLocation
Indicates that one location is geographically or spatially situated below another specified location.
-
B.
upperBranchLocation
Indicates that one entity is located in the upper branch or higher-level subdivision of another entity’s structure or hierarchy.
-
C.
upperCourseOf
Indicates that one watercourse represents the upstream or higher-elevation segment of another watercourse within the same river system.
-
D.
upperAreaName
Indicates that one area is identified by the name of a larger or higher-level area that it belongs to or is contained within.
-
E.
GSSPLocatedIn
chosen
Indicates that something is geographically situated within a specific place or spatial 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_69f224c97a788190b5da1ead6038a74e |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f697eabb048190bc01a830f14942c6 |
completed | May 3, 2026, 12:33 a.m. |
| PD | Predicate disambiguation | batch_69f69664142c8190bc695501056b0236 |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 8:59 p.m.