Triple
T20741531
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chambers of the High Council |
E510452
|
entity |
| Predicate | deliberationStyle |
P66541
|
FINISHED |
| Object | formal 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: formal debate | Statement: [Chambers of the High Council, deliberationStyle, formal debate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deliberationStyle Context triple: [Chambers of the High Council, deliberationStyle, formal debate]
-
A.
deliberativeNature
Indicates that the action or process involves careful consideration, discussion, or weighing of options before reaching a decision.
-
B.
discussionStyle
chosen
Indicates the manner or approach with which one party conducts or participates in a discussion with another.
-
C.
decisionStyle
Indicates the characteristic way an entity approaches, processes, and makes decisions in a given context.
-
D.
settingOfDebate
Indicates the context, environment, or circumstances in which a particular debate takes place.
-
E.
hasDeliberativeFunction
Indicates that an entity serves a role in discussion, consideration, or decision-making processes, typically by participating in or facilitating deliberation.
- 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_69e0b4c845e88190b4c5f3ae79291182 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c20f9670819082199de21a8d9818 |
completed | April 21, 2026, 12:17 a.m. |
| PD | Predicate disambiguation | batch_69e5c0509608819080cdbf47fcddfe36 |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 12:33 p.m.