Triple
T15149550
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trektarbók |
E361899
|
entity |
| Predicate | literaryFormOfTextPreserved |
P6480
|
FINISHED |
| Object | prose |
—
|
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: prose | Statement: [Trektarbók, literaryFormOfTextPreserved, prose]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: literaryFormOfTextPreserved Context triple: [Trektarbók, literaryFormOfTextPreserved, prose]
-
A.
hasLiteraryForm
chosen
Indicates that one entity is expressed, structured, or realized in a particular literary form (such as a genre, style, or textual format).
-
B.
literaryUnit
Indicates that one entity is a distinct segment or component (such as a chapter, scene, or passage) within a larger literary work or text.
-
C.
literaryScript
Indicates a relationship where an entity serves as the written text or script of a literary work, such as a play, film, or other narrative production.
-
D.
literatureType
Indicates the specific category or genre of literature that characterizes or classifies a given work or text.
-
E.
literaryCollection
Indicates that one entity is a collection or compilation of literary works that includes or is associated with the other 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_69d85a0759908190b8a051d2e2a1cbe6 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e005c934048190afac78a8023a544a |
completed | April 15, 2026, 9:40 p.m. |
| PD | Predicate disambiguation | batch_69deb9779acc81908ed2dad382c42dca |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:07 a.m.