Triple
T28515229
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cicero's philosophical dialogues |
E721594
|
entity |
| Predicate | notableInterlocutor |
P6467
|
FINISHED |
| Object | Cicero |
—
|
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: Cicero | Statement: [Cicero's philosophical dialogues, notableInterlocutor, Cicero]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableInterlocutor Context triple: [Cicero's philosophical dialogues, notableInterlocutor, Cicero]
-
A.
notableInterviewee
Indicates that a person has been interviewed by another person or organization in a way considered significant or noteworthy.
-
B.
notableInformant
Indicates that one entity serves as a significant or well-known source of information or testimony for another entity.
-
C.
notableParticipant
chosen
Indicates that an entity plays a significant or distinguished role as a participant in an event, activity, or context.
-
D.
notableFriend
Indicates that one entity is a friend of another in a way that is especially prominent, well-known, or significant.
-
E.
holderNotableFor
Indicates that a holder (such as a person or organization) is particularly known or recognized for a specific role, achievement, work, or characteristic.
- 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_69f01a5c072081908c7b04bcf6478da9 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_6a0127c36dc08190b07765756b3d0e1b |
completed | May 11, 2026, 12:50 a.m. |
| PD | Predicate disambiguation | batch_6a0125ef57208190be5b5e761fcae981 |
completed | May 11, 2026, 12:42 a.m. |
Created at: April 28, 2026, 3:16 a.m.