Triple
T170057
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crusade in Europe |
E3099
|
entity |
| Predicate | hasLaterEdition |
P2686
|
FINISHED |
| Object | paperback edition |
—
|
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: paperback edition | Statement: [Crusade in Europe, hasLaterEdition, paperback edition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLaterEdition Context triple: [Crusade in Europe, hasLaterEdition, paperback edition]
-
A.
laterRepublishedWith
Indicates that an existing work was republished at a later time in a modified or updated form specified by the related entity.
-
B.
nextEdition
chosen
Indicates that one entity is the immediate subsequent edition or version that follows another in a sequence.
-
C.
hasSequel
Indicates that one work is followed by another work that continues its story, timeline, or thematic development.
-
D.
editionNumber
Indicates the specific sequential number assigned to an edition of a work within its series of published versions.
-
E.
notableEdition
Indicates that a particular edition or version of a work is especially significant or noteworthy in relation to that work.
- 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.