Triple
T34147407
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orlické Foothills |
E875898
|
entity |
| Predicate | partOfLargerUnit |
P28620
|
FINISHED |
| Object | Orlická oblast (Orlice area) |
—
|
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: Orlická oblast (Orlice area) | Statement: [Orlické Foothills, partOfLargerUnit, Orlická oblast (Orlice area)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partOfLargerUnit Context triple: [Orlické Foothills, partOfLargerUnit, Orlická oblast (Orlice area)]
-
A.
subunitOf
chosen
Indicates that one entity functions as a component or smaller part within the structure or organization of another, larger entity.
-
B.
hasPartIn
Indicates that an entity participates in or plays a role within a larger event, process, or composite entity.
-
C.
isPeripheralUnitOf
Indicates that one unit functions as a subsidiary or outer component belonging to, and typically supporting, a larger central unit.
-
D.
structurePartOf
Indicates that one structure is a constituent or component of a larger, encompassing structure.
-
E.
containedPartOf
Indicates that one entity is physically or logically included within and forms a part of another entity.
- 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_69f349abaa508190a820f206620efddc |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a002e71bdc48190b922f2d3b362d259 |
completed | May 10, 2026, 7:06 a.m. |
| PD | Predicate disambiguation | batch_6a002e1a28708190b65f9e657c770bab |
completed | May 10, 2026, 7:04 a.m. |
Created at: May 1, 2026, 1:54 a.m.