Triple
T33879067
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Miss Scatcherd |
E868434
|
entity |
| Predicate | disciplinaryStyle |
P18067
|
FINISHED |
| Object | corporal punishment |
—
|
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: corporal punishment | Statement: [Miss Scatcherd, disciplinaryStyle, corporal punishment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: disciplinaryStyle Context triple: [Miss Scatcherd, disciplinaryStyle, corporal punishment]
-
A.
disciplinaryEmphasis
Indicates the primary academic or professional discipline that is emphasized or focused on within a given context.
-
B.
disc1Style
Indicates that one entity has or is characterized by a particular style associated with a first or primary disc.
-
C.
disciplinaryFocus
Indicates the primary academic or professional field, subject area, or discipline that something is centered on or concerned with.
-
D.
disciplinaryMethod
chosen
Indicates a method or approach used to discipline, correct, or control another party’s behavior.
-
E.
methodologicalStyle
Indicates the characteristic approach, techniques, or procedures used in carrying out a method or research process.
- 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_69f34995b81c8190acdb45cea5a10eff |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7051ad6e4819095e82bbd64761803 |
completed | May 3, 2026, 8:19 a.m. |
| PD | Predicate disambiguation | batch_69f700fe24e08190998e2c96fbaaad38 |
completed | May 3, 2026, 8:02 a.m. |
Created at: May 1, 2026, 1:48 a.m.