Triple
T25857696
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Second Lateran Council |
E651393
|
entity |
| Predicate | issuedCanonOn |
P26800
|
FINISHED |
| Object | use of arms by clergy |
—
|
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: use of arms by clergy | Statement: [Second Lateran Council, issuedCanonOn, use of arms by clergy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: issuedCanonOn Context triple: [Second Lateran Council, issuedCanonOn, use of arms by clergy]
-
A.
issuedWith
Indicates that one entity is formally provided, granted, or supplied together with another entity as part of the same issuance event.
-
B.
issuedCanonsOn
chosen
Indicates that an authority formally promulgated or published a set of canons, rules, or decrees on a particular subject or occasion.
-
C.
issuedDocumentOn
Indicates that an entity formally produced or released a document on a specific date or occasion.
-
D.
issuedAct
Indicates that an authority formally created, enacted, or put into effect a specific act, order, or legal instrument.
-
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.
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_69e7ab39035c8190be15c8aaee1bb858 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6430a93a48190854ce71df680b2fa |
completed | May 2, 2026, 6:31 p.m. |
| PD | Predicate disambiguation | batch_69f641da05b881909f6283c988639c53 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 22, 2026, 8:01 a.m.