Triple
T33974313
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aulus Gabinius |
E871087
|
entity |
| Predicate | wasRecalledBy |
P51091
|
FINISHED |
| Object | Julius Caesar |
—
|
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: Julius Caesar | Statement: [Aulus Gabinius, wasRecalledBy, Julius Caesar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasRecalledBy Context triple: [Aulus Gabinius, wasRecalledBy, Julius Caesar]
-
A.
isRecallOf
Indicates that one event, statement, or action serves as a recall, retrieval, or re-mention of a previously occurring or stated event, statement, or action.
-
B.
recalledBy
chosen
Indicates that an entity is brought back, retrieved, or remembered as a result of another entity’s action or prompting.
-
C.
recalledFromOffice
Indicates that an entity has been officially summoned or brought back from its office or post, typically ending or interrupting its assignment there.
-
D.
calledBackBy
Indicates that one entity returns a previous call or contact initiated by another entity.
-
E.
recalledIn
Indicates that an entity is mentioned, remembered, or brought up again within a specific context, such as a document, conversation, or event.
- 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_69f3499da0188190ab1a4ff06fb06a2a |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f70b966860819089cf92927f47c5f1 |
completed | May 3, 2026, 8:47 a.m. |
| PD | Predicate disambiguation | batch_69f70abe43e08190b2a30930d96247c1 |
completed | May 3, 2026, 8:43 a.m. |
Created at: May 1, 2026, 1:50 a.m.