Triple
T1358871
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Count of Vechta |
E29051
|
entity |
| Predicate | usedWithin |
P4341
|
FINISHED |
| Object | feudal system of the Holy Roman Empire |
—
|
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: feudal system of the Holy Roman Empire | Statement: [Count of Vechta, usedWithin, feudal system of the Holy Roman Empire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedWithin Context triple: [Count of Vechta, usedWithin, feudal system of the Holy Roman Empire]
-
A.
usedBetween
Indicates that something serves as a means, medium, or shared resource connecting or operating jointly between two entities.
-
B.
usedDuring
chosen
Indicates that one entity is employed, applied, or active in the course of another entity’s process, event, or time period.
-
C.
usedAt
Indicates that something is employed, applied, or utilized at a particular place, time, or context.
-
D.
usedUntil
Indicates that something remained in use or operation up to a specified time or event, after which it was no longer used.
-
E.
usedWith
Indicates that one entity is typically or appropriately employed together with another entity in a combined or complementary use.
- 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.