Triple
T1358862
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Count of Vechta |
E29051
|
entity |
| Predicate | titleScope |
P25607
|
FINISHED |
| Object | regional |
—
|
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: regional | Statement: [Count of Vechta, titleScope, regional]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleScope Context triple: [Count of Vechta, titleScope, regional]
-
A.
scopeType
chosen
Indicates the specific range, level, or context within which a given relationship, rule, or action is defined or applies.
-
B.
title
Indicates that one entity serves as the formal name or designation of another entity.
-
C.
titleIIFocus
Indicates that the primary focus or subject of a Title II–related provision, requirement, or classification is the referenced entity.
-
D.
titleType
Indicates the specific category or kind of title associated with an entity (e.g., whether it is a main title, alternative title, working title, etc.).
-
E.
scopeDefault
Indicates that something applies or is valid in the absence of a more specific or overriding scope.
- 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_69a498d77abc8190913bf57e5f51d2c4 |
completed | March 1, 2026, 7:51 p.m. |
| NER | Named-entity recognition | batch_69a4c290db288190910fcfa17e902663 |
completed | March 1, 2026, 10:49 p.m. |
| PD | Predicate disambiguation | batch_69a4bef7700c819099b294e8d9320e70 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:56 p.m.