Triple
T31882318
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Caesar |
E813912
|
entity |
| Predicate | triumvirateMemberWith |
P26927
|
FINISHED |
| Object | Pompey |
—
|
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: Pompey | Statement: [Caesar, triumvirateMemberWith, Pompey]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: triumvirateMemberWith Context triple: [Caesar, triumvirateMemberWith, Pompey]
-
A.
triadMemberWith
chosen
Indicates a relationship where an entity is a member of a specific triad together with two other associated entities.
-
B.
officeStartAsTriumvir
Indicates that an entity begins holding an office or position specifically in the role of a triumvir (one of three joint officeholders).
-
C.
foundingMemberAlongside
Indicates that an entity was a founding member of an organization or group together with one or more specified other entities at the time of its establishment.
-
D.
constituentPeople
Indicates that certain people collectively make up or form part of a larger group, body, or organization.
-
E.
boardMember
Indicates that a person serves on the governing board of an organization, participating in its oversight and decision-making.
- 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_69f348ed74bc81909846aaa6a3c7318c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6b0d7e7508190a4b932d93ca4d276 |
completed | May 3, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_69f6aca59d4881908d14ed47962703bd |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 30, 2026, 11:56 p.m.