Triple
T316059
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nuskhuri |
E7708
|
entity |
| Predicate | caseUsage |
P2529
|
FINISHED |
| Object | lowercase in ecclesiastical writing |
—
|
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: lowercase in ecclesiastical writing | Statement: [Nuskhuri, caseUsage, lowercase in ecclesiastical writing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: caseUsage Context triple: [Nuskhuri, caseUsage, lowercase in ecclesiastical writing]
-
A.
letterCase
Indicates the relationship between a character or string and its typographical case (such as uppercase, lowercase, or mixed case).
-
B.
usageType
chosen
Indicates the specific manner, purpose, or context in which something is used or intended to be used.
-
C.
hasCase
Indicates that one entity is involved in, associated with, or characterized by a particular case, instance, or occurrence represented by another entity.
-
D.
actualUse
Indicates that an entity is currently being used or utilized in practice, as opposed to being merely available, planned, or potential.
-
E.
majorCase
Indicates that a legal case is of primary importance or high significance within a given context.
- 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_69a2e7e7af7881908890039d6be4e9b8 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ea6462148190825acc57f6d2adaf |
completed | Feb. 28, 2026, 1:15 p.m. |
| PD | Predicate disambiguation | batch_69a2e943f12c8190883854aeed974260 |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.