Triple
T561751
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Runic alphabet |
E13465
|
entity |
| Predicate | continuedLimitedUseUntil |
P6544
|
FINISHED |
| Object | early modern period |
—
|
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: early modern period | Statement: [Runic alphabet, continuedLimitedUseUntil, early modern period]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: continuedLimitedUseUntil Context triple: [Runic alphabet, continuedLimitedUseUntil, early modern period]
-
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.
subsequentUse
Indicates that one entity is used, applied, or consumed after another entity in time or sequence.
-
C.
usedDuring
Indicates that one entity is employed, applied, or active in the course of another entity’s process, event, or time period.
-
D.
usedSince
Indicates that an entity has been in use starting from a specified point in time and continuing thereafter.
-
E.
eligibleUses
Indicates the types of actions, purposes, or contexts in which something is permitted or qualified to be used.
- 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_69a4933edcf08190b35ecfd6014caee6 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49a700e608190b235246df057bd9b |
completed | March 1, 2026, 7:58 p.m. |
| PD | Predicate disambiguation | batch_69a494befb8481908bb4e2e9f31e343b |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:32 p.m.