Triple
T15772660
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reykjabók |
E382399
|
entity |
| Predicate | hasWorkTypePreserved |
P104843
|
FINISHED |
| Object | prose narrative |
—
|
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 narrative | Statement: [Reykjabók, hasWorkTypePreserved, prose narrative]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWorkTypePreserved Context triple: [Reykjabók, hasWorkTypePreserved, prose narrative]
-
A.
hasWorkTypeRelation
chosen
Indicates a relationship specifying the type or category of work associated with an entity.
-
B.
hasPreservationType
Indicates the specific method or category of preservation applied to an entity (e.g., how it is stored, conserved, or kept intact).
-
C.
hasWorkAdaptationType
Indicates the type of adaptation or modification applied to a work (e.g., translation, abridgment, dramatization) in relation to its original form.
-
D.
hasWorkPart
Indicates that one work is a component, section, or constituent part of another, larger work.
-
E.
hasWorkAdaptedBy
Indicates that one work has been transformed or re-created into another work, such as through adaptation into a different medium or format.
- 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_69d86da09a10819082fe9797b23e4664 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e051976d248190adddd3db9f758e22 |
completed | April 16, 2026, 3:03 a.m. |
| PD | Predicate disambiguation | batch_69e00531e7ac8190a4190cce4f7fab4c |
completed | April 15, 2026, 9:37 p.m. |
Created at: April 10, 2026, 4:47 a.m.