Triple
T16517501
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Capitula of Orange |
E401221
|
entity |
| Predicate | canonicalForm |
P45461
|
FINISHED |
| Object | series of canons |
—
|
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: series of canons | Statement: [Capitula of Orange, canonicalForm, series of canons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canonicalForm Context triple: [Capitula of Orange, canonicalForm, series of canons]
-
A.
isCanonicalFormOf
Indicates that one entity is the standard or officially accepted form or representation of another, often more variant, entity.
-
B.
hasCanonicalFormulation
Indicates that one entity is the standard or officially accepted formulation or expression of another entity.
-
C.
canonicalText
chosen
Indicates that a standardized, authoritative textual representation is associated with an entity or expression.
-
D.
canonicalVarieties
Indicates that one entity is a canonical or standard variety/form of another entity within a given classification or system.
-
E.
standardFormulation
Indicates that something is expressed or represented in a conventional, officially accepted, or commonly used form or version.
- 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_69d883838abc8190bc79cb2d41733ce2 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32e7da2248190a540a5ef8686963d |
completed | April 18, 2026, 7:10 a.m. |
| PD | Predicate disambiguation | batch_69e296995d388190b88ebe189dce890d |
completed | April 17, 2026, 8:22 p.m. |
Created at: April 10, 2026, 5:14 a.m.