Triple
T10126003
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mynheer Peeperkorn |
E226215
|
entity |
| Predicate | hasCommunicationStyle |
P83331
|
FINISHED |
| Object | rambling speeches |
—
|
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: rambling speeches | Statement: [Mynheer Peeperkorn, hasCommunicationStyle, rambling speeches]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCommunicationStyle Context triple: [Mynheer Peeperkorn, hasCommunicationStyle, rambling speeches]
-
A.
communicationTrait
chosen
Indicates a characteristic or quality related to how an entity communicates or engages in communication.
-
B.
hasDecisionMakingStyle
Indicates that an entity possesses or exhibits a particular way or pattern of making decisions.
-
C.
communicationMode
Indicates the method or channel through which communication between entities is carried out.
-
D.
communicatedAs
Indicates that one entity is expressed, conveyed, or presented in the form, manner, or role of another.
-
E.
usedToCommunicate
Indicates that one entity serves as a medium or tool through which another entity conveys information, messages, or signals.
- 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_69ca843057b48190a86730167f5d6b98 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cdd2ed85b4819097dfe89e044e1a90 |
completed | April 2, 2026, 2:22 a.m. |
| PD | Predicate disambiguation | batch_69cd4ba1d360819087698d04a53cc87e |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 9:05 p.m.