Triple
T29586482
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Book II: The People of God |
E754035
|
entity |
| Predicate | containsCanonsTo |
P197555
|
FINISHED |
| Object | canon 746 |
—
|
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: canon 746 | Statement: [Book II: The People of God, containsCanonsTo, canon 746]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsCanonsTo Context triple: [Book II: The People of God, containsCanonsTo, canon 746]
-
A.
containsCanonsFrom
Indicates that one entity includes or incorporates canons that originate from another entity.
-
B.
implementedInCanons
Indicates that something is realized, expressed, or carried out within a set of established rules, standards, or canonical works.
-
C.
usesCodeOfCanons
Indicates that one entity applies, follows, or is governed by a specified code of canons (a formal set of rules or laws).
-
D.
inCanonWith
Indicates that two or more works, events, or elements are officially recognized as belonging to the same narrative continuity or canon.
-
E.
inCanonOf
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. chosen
Provenance (4 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_69f0ef836ac88190bd809dc58b5ec907 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69fe9b0276d48190b554fa22b043e6d8 |
completed | May 9, 2026, 2:25 a.m. |
| PD | Predicate disambiguation | batch_69fe999692b081909921e1148d66f0ef |
completed | May 9, 2026, 2:19 a.m. |
| PDg | Predicate description generation | batch_69fe9b013ec481908f89beddb9c4cd4e |
completed | May 9, 2026, 2:25 a.m. |
Created at: April 28, 2026, 6:11 p.m.