Triple
T25860430
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deipnosophistae |
E651462
|
entity |
| Predicate | frameNarrativeAddressee |
P159833
|
FINISHED |
| Object | Timocrates |
—
|
NE NERFINISHED |
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: Timocrates | Statement: [Deipnosophistae, frameNarrativeAddressee, Timocrates]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: frameNarrativeAddressee Context triple: [Deipnosophistae, frameNarrativeAddressee, Timocrates]
-
A.
narrativeCharacter
Indicates that one entity functions as a character within the narrative or story associated with another entity.
-
B.
narrativeFrame
Indicates the overarching narrative context or perspective within which events, actions, or relationships are presented or interpreted.
-
C.
inNarrativeRole
Indicates that one entity participates in relation to another by occupying a specific narrative function or role within a story or discourse.
-
D.
narrativeSourceCharacter
Indicates that a particular character serves as the source or narrator from whose perspective the narrative is presented.
-
E.
narrativeSubject
Indicates that an entity functions as the main subject or focal point within a narrative or story.
- F. None of above. chosen
Provenance (4 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_69f6026b467c8190a1f8be336f8679da |
completed | May 2, 2026, 1:55 p.m. |
| PD | Predicate disambiguation | batch_69f5afec3e94819080d9ba86cf8c866e |
completed | May 2, 2026, 8:03 a.m. |
| PDg | Predicate description generation | batch_69f5f6b32a8881909baa0db57b80d56a |
completed | May 2, 2026, 1:05 p.m. |
Created at: April 22, 2026, 8:05 a.m.