Triple
T170056
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crusade in Europe |
E3099
|
entity |
| Predicate | originallyPublishedFormat |
P130
|
FINISHED |
| Object | hardcover |
—
|
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: hardcover | Statement: [Crusade in Europe, originallyPublishedFormat, hardcover]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originallyPublishedFormat Context triple: [Crusade in Europe, originallyPublishedFormat, hardcover]
-
A.
originallyWrittenFor
Indicates that a work was initially created or composed with a particular recipient, medium, context, or purpose in mind.
-
B.
publishedIn
Indicates that a work (such as an article, paper, or book) has been formally released or made available within a specific venue, medium, or publication.
-
C.
format
chosen
Indicates the specific arrangement, structure, or presentation style in which something is organized or expressed.
-
D.
publishedFor
Indicates that something (such as a work, document, or content) is published with a particular audience, recipient, or target group in mind.
-
E.
originalType
Indicates that one entity represents the initial or source type from which another entity is derived, transformed, or reclassified.
- 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_69a2524ce1e48190ab066bf72859f474 |
completed | Feb. 28, 2026, 2:26 a.m. |
| NER | Named-entity recognition | batch_69a25a3f9d188190aacf5791273e2c65 |
completed | Feb. 28, 2026, 3 a.m. |
| PD | Predicate disambiguation | batch_69a25667717c8190bac5108366e2178d |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:34 a.m.