Triple
T8549377
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kuruntokai |
E202406
|
entity |
| Predicate | modernMedium |
P51716
|
FINISHED |
| Object | printed editions |
—
|
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: printed editions | Statement: [Kuruntokai, modernMedium, printed editions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: modernMedium Context triple: [Kuruntokai, modernMedium, printed editions]
-
A.
subsequentMedium
Indicates that one medium or format follows another in a sequence, typically as a later or alternative form of the same content or communication.
-
B.
commonMedium
Indicates that two or more entities share the same medium or channel through which interaction, communication, or transmission occurs.
-
C.
secondaryMedium
Indicates that an entity is associated with an additional, non-primary medium or channel through which it is expressed, delivered, or communicated.
-
D.
primaryMedium
Indicates the main material, format, or channel through which something is created, expressed, or communicated.
-
E.
mediumCategory
chosen
Indicates the classification of an item or content according to the type or form of medium it belongs to (e.g., print, digital, audio, video).
- 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_69ca832610e08190b3b6c6cd2c250255 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe753d3608190b0573477182cf194 |
completed | March 31, 2026, 3:25 p.m. |
| PD | Predicate disambiguation | batch_69cbd113e05c81908f4f3fc1b5925164 |
completed | March 31, 2026, 1:50 p.m. |
Created at: March 30, 2026, 6:19 p.m.