Triple
T33049769
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hiketides |
E845690
|
entity |
| Predicate | currentMedium |
P5765
|
FINISHED |
| Object | written text |
—
|
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: written text | Statement: [Hiketides, currentMedium, written text]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currentMedium Context triple: [Hiketides, currentMedium, written text]
-
A.
canonicalMedium
Indicates the primary or standard medium through which something is most authoritatively or typically expressed, distributed, or experienced.
-
B.
targetMedium
Indicates the medium or channel through which an action, message, or effect is directed or intended to be delivered.
-
C.
primaryMedium
chosen
Indicates the main material, format, or channel through which something is created, expressed, or communicated.
-
D.
circulationMedium
Indicates the medium or channel through which something (such as information, materials, or currency) is distributed, transmitted, or made to move.
-
E.
applicableMedium
Indicates that a particular medium or material is suitable for use with, or can be effectively applied by, the referenced entity.
- 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_69f3495242e48190996a2cb2beab5455 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fef3ceef648190b58027c93d757438 |
completed | May 9, 2026, 8:43 a.m. |
| PD | Predicate disambiguation | batch_69fef359da2c819091a034387b08821f |
completed | May 9, 2026, 8:42 a.m. |
Created at: May 1, 2026, 1:24 a.m.