Triple
T23142616
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Naive Bayes classifier |
E577500
|
entity |
| Predicate | typicalDecisionRule |
P35633
|
FINISHED |
| Object | maximum a posteriori decision rule |
—
|
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: maximum a posteriori decision rule | Statement: [Naive Bayes classifier, typicalDecisionRule, maximum a posteriori decision rule]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalDecisionRule Context triple: [Naive Bayes classifier, typicalDecisionRule, maximum a posteriori decision rule]
-
A.
decisionMakingRule
chosen
Indicates the principle, guideline, or procedure that governs how a decision is made in a given context.
-
B.
decisionType
Indicates the specific category or nature of a decision associated with an entity or event.
-
C.
makesDecisionBy
Indicates that one entity determines or chooses an outcome, course of action, or judgment by means of another entity, method, or process.
-
D.
decisionStyle
Indicates the characteristic way an entity approaches, processes, and makes decisions in a given context.
-
E.
decisionLanguage
Indicates that a decision, statement, or choice is expressed or recorded in a particular natural language.
- 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_69e245f8e6248190ba3d58e068b4dccb |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18ecb72fc8190a24e8f5756217a36 |
completed | April 29, 2026, 4:53 a.m. |
| PD | Predicate disambiguation | batch_69ef89f83b108190aaaa1db6221fc163 |
completed | April 27, 2026, 4:08 p.m. |
Created at: April 17, 2026, 4 p.m.