Triple
T8300215
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sumerian language |
E194331
|
entity |
| Predicate | remainedInUseAs |
P2451
|
FINISHED |
| Object | liturgical language |
—
|
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: liturgical language | Statement: [Sumerian language, remainedInUseAs, liturgical language]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: remainedInUseAs Context triple: [Sumerian language, remainedInUseAs, liturgical language]
-
A.
stillUsedBy
Indicates that something continues to be used or relied upon by another entity at the present time.
-
B.
usedAt
Indicates that something is employed, applied, or utilized at a particular place, time, or context.
-
C.
areUsedSince
Indicates that entities have been in use continuously starting from a specified point in time.
-
D.
usedDuring
Indicates that one entity is employed, applied, or active in the course of another entity’s process, event, or time period.
-
E.
inUseSince
chosen
Indicates that an entity has been actively in use starting from a specified point in time.
- 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_69ca82e50ebc81909aa7b260c76bd757 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7e879c588190a6f95cf7795541ad |
completed | March 31, 2026, 7:57 a.m. |
| PD | Predicate disambiguation | batch_69cb70b5b5348190b296e0ecec95de60 |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 5:53 p.m.