Triple
T896586
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Homer |
E19359
|
entity |
| Predicate | traditionallyCreditedWith |
P6838
|
FINISHED |
| Object | composing the Iliad |
—
|
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: composing the Iliad | Statement: [Homer, traditionallyCreditedWith, composing the Iliad]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionallyCreditedWith Context triple: [Homer, traditionallyCreditedWith, composing the Iliad]
-
A.
creditedFor
Indicates that one entity is acknowledged as the source, contributor, or originator responsible for another entity (such as a work, achievement, or outcome).
-
B.
originalArtistNameCredit
Indicates that the credited name refers to the artist who originally created the work or recording.
-
C.
namedForNotableWork
Indicates that one entity is named in honor of another entity’s notable work or achievement.
-
D.
traditionallyOneOf
Indicates that something is customarily or historically considered to belong to a specific set, category, or group.
-
E.
traditionalAuthorship
chosen
Indicates that an entity is recognized as the conventional or historically accepted author of a work, according to traditional attribution.
- 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_69a4939d37188190848be3d426ebc9ae |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ad2550c88190a624eb5627d472ad |
completed | March 1, 2026, 9:18 p.m. |
| PD | Predicate disambiguation | batch_69a4aa94f7c881908deeb62308942e19 |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:39 p.m.