Triple
T28728965
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Second session of the Second Vatican Council |
E730302
|
entity |
| Predicate | hasTypeOfDebate |
P193115
|
FINISHED |
| Object | doctrinal debate |
—
|
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: doctrinal debate | Statement: [Second session of the Second Vatican Council, hasTypeOfDebate, doctrinal debate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeOfDebate Context triple: [Second session of the Second Vatican Council, hasTypeOfDebate, doctrinal debate]
-
A.
hasDebate
Indicates that there is a formal discussion or argument between entities, typically presenting opposing viewpoints on a topic.
-
B.
hasDebateAround
Indicates that there is ongoing discussion, disagreement, or controversy surrounding the referenced entity or topic.
-
C.
hasDebateFormat
Indicates that a particular debate, event, or context uses or follows a specified debate format or structure.
-
D.
areDebatesOf
Indicates that the subject entities are debates that concern, involve, or are associated with the object entities.
-
E.
hasDebateTerm
Indicates that an entity is associated with, or characterized by, a specific term used in a debate or argumentative context.
- 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_69f043e91fe48190b73bcd8e08d433e0 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69fd389cb28c819099a77e28d25f258a |
completed | May 8, 2026, 1:13 a.m. |
| PD | Predicate disambiguation | batch_69fd3826d8048190ada79a5868d1d7f3 |
completed | May 8, 2026, 1:11 a.m. |
| PDg | Predicate description generation | batch_69fd389b653c81908a97ab2eff98c6ea |
completed | May 8, 2026, 1:12 a.m. |
Created at: April 28, 2026, 5:57 a.m.