Triple
T29586427
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Book I: General Norms |
E754034
|
entity |
| Predicate | beginsWithCanon |
P167482
|
FINISHED |
| Object | canon 1 |
—
|
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 1 | Statement: [Book I: General Norms, beginsWithCanon, canon 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: beginsWithCanon Context triple: [Book I: General Norms, beginsWithCanon, canon 1]
-
A.
inCanonWith
Indicates that two or more works, events, or elements are officially recognized as belonging to the same narrative continuity or canon.
-
B.
usesCanon
Indicates that one entity employs or relies on another entity as its standard, reference, or authoritative source.
-
C.
beganWith
Indicates that one event, process, or state started with or was initiated by another specified event, process, or state.
-
D.
inCanonOf
Indicates that one entity is officially recognized as part of the established canon or authoritative body of works associated with another entity.
-
E.
givesCanon
Indicates that one entity provides or establishes an official or authoritative version (canon) of something for another entity or context.
- 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_69f66d7dfb948190b35070cef785d6b8 |
completed | May 2, 2026, 9:32 p.m. |
| PD | Predicate disambiguation | batch_69f6659d36208190b01412600a4ed57d |
completed | May 2, 2026, 8:59 p.m. |
| PDg | Predicate description generation | batch_69f6691da93081909deaf680614fc900 |
completed | May 2, 2026, 9:14 p.m. |
Created at: April 28, 2026, 6:11 p.m.