Triple
T15687397
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OHV |
E380236
|
entity |
| Predicate | belongsToRegionCategory |
P97770
|
FINISHED |
| Object | Landkreis |
—
|
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: Landkreis | Statement: [OHV, belongsToRegionCategory, Landkreis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToRegionCategory Context triple: [OHV, belongsToRegionCategory, Landkreis]
-
A.
collectionIncludesRegion
Indicates that a collection contains or encompasses a specified region as one of its constituent parts.
-
B.
hasRegion
Indicates that an entity includes, contains, or is associated with a specific geographic or administrative region as part of its scope or structure.
-
C.
containsRegionType
chosen
Indicates that one region includes or encompasses another region of a specified type within its spatial or logical boundaries.
-
D.
isRegionOf
Indicates that one entity is a geographic or administrative region belonging to, contained within, or associated with another entity.
-
E.
meetsInRegion
Indicates that two or more entities encounter or come together within a specified geographic 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_69d86d99e860819094b6957cde470f2c |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e04f4cee5481908699fbb2b7bdd2f6 |
completed | April 16, 2026, 2:54 a.m. |
| PD | Predicate disambiguation | batch_69deda8c856c8190882330114f9a1a5f |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:44 a.m.