Triple
T25870625
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Runo XX |
E651743
|
entity |
| Predicate | hasLaterMedium |
P78290
|
FINISHED |
| Object | printed book |
—
|
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 book | Statement: [Runo XX, hasLaterMedium, printed book]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLaterMedium Context triple: [Runo XX, hasLaterMedium, printed book]
-
A.
hasPageMedium
Indicates that a page or document is associated with a particular physical or digital medium through which it is presented or stored.
-
B.
hasMediumCharacter
Indicates that one entity possesses or is associated with a character whose size, intensity, or degree is classified as medium.
-
C.
subsequentMedium
chosen
Indicates that one medium or format follows another in a sequence, typically as a later or alternative form of the same content or communication.
-
D.
hasLaterTitle
Indicates that one title occurs chronologically after another title in a sequence or timeline.
-
E.
hasLaterCapital
Indicates that one entity’s designation or establishment as a capital city occurred later in time than that of another 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_69e7ab3ad9d88190841ddcb93ab02e96 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6c49627908190b3553474c7c3072b |
completed | May 3, 2026, 3:44 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f23ae081909a52801266063a3c |
completed | May 3, 2026, 3:41 a.m. |
Created at: April 22, 2026, 8:11 a.m.