Triple
T28767887
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ellie Bishop |
E726326
|
entity |
| Predicate | predecessorOnTeam |
P14604
|
FINISHED |
| Object | Ziva David |
—
|
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: Ziva David | Statement: [Ellie Bishop, predecessorOnTeam, Ziva David]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: predecessorOnTeam Context triple: [Ellie Bishop, predecessorOnTeam, Ziva David]
-
A.
predecessorTeamContext
Indicates that one team context directly precedes another in a sequence or timeline of team configurations or states.
-
B.
predecessorInRole
chosen
Indicates that one entity previously held a particular role or position that was later occupied by another entity.
-
C.
predecessorUser
Indicates that one user previously held a role, position, or state that is now held by another user, making the first user the predecessor of the second.
-
D.
predecessorName
Indicates that the value is the name of an entity that directly precedes another in an ordered sequence or lineage.
-
E.
predecessorManagedBy
Indicates that a predecessor entity was managed, overseen, or administered by another entity.
- 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_69f03198be14819098fa74e48b3749bf |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f7465687bc8190a9da44d62b634ed7 |
completed | May 3, 2026, 12:57 p.m. |
| PD | Predicate disambiguation | batch_69f743f4ceb08190a21fe7f4a99b166b |
completed | May 3, 2026, 12:47 p.m. |
Created at: April 28, 2026, 6:14 a.m.