Triple
T33362118
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Extravagantes Communes |
E854248
|
entity |
| Predicate | hasStructureModelledOn |
P149676
|
FINISHED |
| Object | Decretals of Gregory IX |
—
|
NE NERFINISHED |
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: Decretals of Gregory IX | Statement: [Extravagantes Communes, hasStructureModelledOn, Decretals of Gregory IX]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStructureModelledOn Context triple: [Extravagantes Communes, hasStructureModelledOn, Decretals of Gregory IX]
-
A.
modeledWith
Indicates that something is represented, simulated, or described using a particular model, method, or modeling technique.
-
B.
isModelledAfter
chosen
Indicates that one entity is created, designed, or structured based on the form, features, or principles of another entity.
-
C.
hasHumanStructure
Indicates that one entity possesses or exhibits a structural form or organization characteristic of humans.
-
D.
designedStructureType
Indicates the type or category of structure that something has been specifically designed to be.
-
E.
haveStructure
Indicates that an entity possesses a particular internal organization, arrangement, or structural composition.
- 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_69f3496bda8c8190bfc8fade9d1b791c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff46afe7e481908f2862ed11c88db2 |
completed | May 9, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69ff45e9151881909c444a655e852165 |
completed | May 9, 2026, 2:34 p.m. |
Created at: May 1, 2026, 1:34 a.m.