Triple
T25050299
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ex illa die |
E627358
|
entity |
| Predicate | documentFamily |
P157581
|
FINISHED |
| Object | apostolic constitutions of the Catholic Church |
—
|
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: apostolic constitutions of the Catholic Church | Statement: [Ex illa die, documentFamily, apostolic constitutions of the Catholic Church]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: documentFamily Context triple: [Ex illa die, documentFamily, apostolic constitutions of the Catholic Church]
-
A.
documentForm
Indicates the specific format or structural type in which a document is presented or recorded.
-
B.
documentationType
Indicates the specific category or kind of documentation associated with or required for an entity or process.
-
C.
documentsNow
Indicates that an entity is currently documenting, recording, or writing about another entity at the present time.
-
D.
documentsTypeOfWork
Indicates that one entity records or specifies the category or type of work associated with another entity.
-
E.
documentsCommunity
Indicates that an entity records, describes, or provides information about a particular community.
- 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_69e2ff2b4c80819087c916b2b16241b9 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f454a02ac88190ae0a2ac9071622eb |
completed | May 1, 2026, 7:22 a.m. |
| PD | Predicate disambiguation | batch_69f442c861188190967655c6d8012380 |
completed | May 1, 2026, 6:06 a.m. |
| PDg | Predicate description generation | batch_69f448fe11f08190bdd53ca7ba2d51e4 |
completed | May 1, 2026, 6:32 a.m. |
Created at: April 18, 2026, 6:09 a.m.