Triple
T8338931
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Third session of the Second Vatican Council |
E195859
|
entity |
| Predicate | documentTypePromulgated |
P44878
|
FINISHED |
| Object | dogmatic constitution |
—
|
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: dogmatic constitution | Statement: [Third session of the Second Vatican Council, documentTypePromulgated, dogmatic constitution]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: documentTypePromulgated Context triple: [Third session of the Second Vatican Council, documentTypePromulgated, dogmatic constitution]
-
A.
documentTypeProduced
Indicates that one entity produces, generates, or creates a document of a specified type.
-
B.
documentTypePublished
chosen
Indicates that a specific type or category of document has been formally published or made publicly available.
-
C.
documentationType
Indicates the specific category or kind of documentation associated with or required for an entity or process.
-
D.
documentTypeUsed
Indicates that a particular type or category of document is employed or applied in a given context or activity.
-
E.
regulatoryDocument
Indicates a relationship where one entity serves as a regulatory document that defines rules, standards, or requirements governing 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_69ca82ecbdc481908a55cad8ca062d88 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7fd68e348190a7cb8639a263b50f |
completed | March 31, 2026, 8:03 a.m. |
| PD | Predicate disambiguation | batch_69cb70c6d0ec8190acf273b0e007b51a |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 5:57 p.m.