Triple
T10164165
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Liber Iudiciorum |
E233964
|
entity |
| Predicate | wasUsedUntil |
P6544
|
FINISHED |
| Object | well into the Middle Ages in Christian kingdoms of Iberia |
—
|
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: well into the Middle Ages in Christian kingdoms of Iberia | Statement: [Liber Iudiciorum, wasUsedUntil, well into the Middle Ages in Christian kingdoms of Iberia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasUsedUntil Context triple: [Liber Iudiciorum, wasUsedUntil, well into the Middle Ages in Christian kingdoms of Iberia]
-
A.
usedUntil
chosen
Indicates that something remained in use or operation up to a specified time or event, after which it was no longer used.
-
B.
usedAt
Indicates that something is employed, applied, or utilized at a particular place, time, or context.
-
C.
lastUsedFor
Indicates that one entity was the most recent purpose, function, or application for which another entity was used.
-
D.
areUsedSince
Indicates that entities have been in use continuously starting from a specified point in time.
-
E.
usedSince
Indicates that an entity has been in use starting from a specified point in time and continuing thereafter.
- 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_69ca848e80748190b91d1e04d35512c7 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cdec6a7bb48190952f4318af9cc32b |
completed | April 2, 2026, 4:11 a.m. |
| PD | Predicate disambiguation | batch_69cd4ba795808190acc9124c98c6e40f |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 9:09 p.m.