Triple
T2018150
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pearl of Great Price |
E44042
|
entity |
| Predicate | partOfCanon |
P977
|
FINISHED |
| Object | standard works |
—
|
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: standard works | Statement: [Pearl of Great Price, partOfCanon, standard works]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partOfCanon Context triple: [Pearl of Great Price, partOfCanon, standard works]
-
A.
followsInCanon
Indicates that one entity occurs later than and in continuity with another within an established narrative or canonical sequence.
-
B.
notInCanonOf
Indicates that something is excluded from, or does not belong to, the officially recognized canon of a given work or universe.
-
C.
partOfTrilogy
Indicates that one work belongs to a set of three related works that together form a trilogy.
-
D.
partOfFranchiseLineage
Indicates that one entity belongs to, or is derived from, the same overarching franchise lineage as another entity, reflecting continuity within a shared franchise.
-
E.
inCanonOf
chosen
Indicates that one entity is officially recognized as part of the established canon or authoritative body of works associated with 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_69a8891201bc8190aca837be6de41579 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abb8ce71788190ac21beff10b08122 |
completed | March 7, 2026, 5:34 a.m. |
| PD | Predicate disambiguation | batch_69abb7a389408190a84a54856352f15b |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:38 p.m.