Triple
T3511936
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eryximachus |
E74215
|
entity |
| Predicate | givesSpeechOn |
P48429
|
FINISHED |
| Object | love |
—
|
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: love | Statement: [Eryximachus, givesSpeechOn, love]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: givesSpeechOn Context triple: [Eryximachus, givesSpeechOn, love]
-
A.
spokenOn
Indicates that an utterance or speech act occurred at or during a specific time or date.
-
B.
spokeAt
Indicates that a person delivered a talk, speech, or presentation at a particular event or location.
-
C.
alsoSpeak
Indicates that an entity, in addition to another language or mode of communication already mentioned, speaks this additional language or communicates in this additional way.
-
D.
spokenAlong
Indicates that two or more languages are used concurrently or within the same context in a particular place, time, or situation.
-
E.
succeededAsSpeakerBy
Indicates that one entity took over the role or position of speaker from another entity as their successor.
- 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_69ad85cfb5c881909c9a2edd9d6043cc |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbc10b6b48190bedfed6d34afc425 |
completed | March 8, 2026, 6:12 p.m. |
| PD | Predicate disambiguation | batch_69adae0e770481908528fa35eda53003 |
completed | March 8, 2026, 5:12 p.m. |
| PDg | Predicate description generation | batch_69adaed74ecc8190b74dc70ab59a3e1c |
completed | March 8, 2026, 5:16 p.m. |
Created at: March 8, 2026, 3:19 p.m.