Triple
T25860385
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ἀθήναιος |
E651461
|
entity |
| Predicate | subjectOfNotableWork |
P4941
|
FINISHED |
| Object | erudition |
—
|
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: erudition | Statement: [Ἀθήναιος, subjectOfNotableWork, erudition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subjectOfNotableWork Context triple: [Ἀθήναιος, subjectOfNotableWork, erudition]
-
A.
notableWorkSubject
chosen
Indicates that a work is notably associated with a particular subject, such as a person, topic, or entity, as its primary focus or theme.
-
B.
namedForNotableWork
Indicates that one entity is named in honor of another entity’s notable work or achievement.
-
C.
notableWorkAs
Indicates a relationship where a particular work is recognized as a significant or distinguished creation associated with an entity.
-
D.
notableWorkIn
Indicates that an entity is known for or associated with a significant work, contribution, or achievement in a particular field or context.
-
E.
notableWorkAuthor
Indicates that one entity is the creator or author of a notable work associated with another entity.
- 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_69e7ab3a199c81909227cb964cacfe24 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6352fdb788190b9bad30243690743 |
completed | May 2, 2026, 5:32 p.m. |
| PD | Predicate disambiguation | batch_69f63182f1408190bddc1214fcbd6145 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 22, 2026, 8:05 a.m.