Triple
T29586426
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Book I: General Norms |
E754034
|
entity |
| Predicate | hasCanonicalRange |
P27293
|
FINISHED |
| Object | canons 1–203 |
—
|
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: canons 1–203 | Statement: [Book I: General Norms, hasCanonicalRange, canons 1–203]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCanonicalRange Context triple: [Book I: General Norms, hasCanonicalRange, canons 1–203]
-
A.
hasRange
chosen
Indicates that a property or relation is constrained to take its values from a specified class, type, or value set.
-
B.
hasCanonicalLength
Indicates that something possesses a standard or officially defined length used as a reference or norm.
-
C.
hasCanonicalRepresentation
Indicates that one entity is the standard or authoritative form in which another entity is represented.
-
D.
hasCanonicalNumber
Indicates that an entity is associated with its officially recognized or standard reference number.
-
E.
hasCanonicalContinuity
Indicates that one entity’s storyline, version, or depiction is officially recognized as part of the primary, authoritative continuity of another entity or universe.
- 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_69f0ef836ac88190bd809dc58b5ec907 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69fd6dbd1b648190b1a0b391c03aebc5 |
completed | May 8, 2026, 4:59 a.m. |
| PD | Predicate disambiguation | batch_69fd6a9020548190bbfa845360ac85fb |
completed | May 8, 2026, 4:46 a.m. |
Created at: April 28, 2026, 6:11 p.m.