Triple
T3591516
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sophists |
E76034
|
entity |
| Predicate | taughtAudience |
P11007
|
FINISHED |
| Object | young aristocratic men |
—
|
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: young aristocratic men | Statement: [Sophists, taughtAudience, young aristocratic men]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: taughtAudience Context triple: [Sophists, taughtAudience, young aristocratic men]
-
A.
typicalAudience
Indicates the group of people for whom something (such as a work, product, or resource) is primarily intended or most suitable.
-
B.
taughtAs
Indicates that one entity served as a teacher or instructor for another entity in an educational or training context.
-
C.
hasEducationalAudience
Indicates that something is intended for or directed toward a specific educational audience or learner group.
-
D.
targetStudentGroup
chosen
Indicates a relationship where something is directed, tailored, or intended specifically for a particular group of students.
-
E.
taughtThrough
Indicates that one entity provided instruction, education, or training to another entity by means of a specified method, medium, or intermediary.
- 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_69ad85d8042081908af94a04c410dec0 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc1581278819081dd73b4c71e422e |
completed | March 8, 2026, 6:35 p.m. |
| PD | Predicate disambiguation | batch_69adb839b4e08190b1c0d611cccb11ae |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:22 p.m.