Triple
T31816797
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Der gebildete Mensch |
E812156
|
entity |
| Predicate | educationalPerspective |
P779
|
FINISHED |
| Object | humanistic education |
—
|
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: humanistic education | Statement: [Der gebildete Mensch, educationalPerspective, humanistic education]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: educationalPerspective Context triple: [Der gebildete Mensch, educationalPerspective, humanistic education]
-
A.
educationalApproach
chosen
Indicates the method, strategy, or philosophy used to guide teaching and learning within an educational context.
-
B.
educationalImportance
Indicates the degree to which something is significant, valuable, or impactful in an educational or learning context.
-
C.
educationalImpact
Indicates the effect or influence that one entity has on the learning, knowledge, or educational outcomes of another.
-
D.
educationalFocus
Indicates the primary subject area or theme that an educational activity, program, or resource is centered on.
-
E.
educationalContext
Indicates the situational or institutional setting in which an educational activity, interaction, or resource takes place.
- 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_69f348e846c081908eb468a0665afd55 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f707f7959881908f037f0d6b1d0c36 |
completed | May 3, 2026, 8:31 a.m. |
| PD | Predicate disambiguation | batch_69f700fc274c8190a128593dc7c7abd0 |
completed | May 3, 2026, 8:02 a.m. |
Created at: April 30, 2026, 11:44 p.m.