Triple
T29187787
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tam Ryvora |
E739915
|
entity |
| Predicate | laterJoins |
P23692
|
FINISHED |
| Object | Resistance |
—
|
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: Resistance | Statement: [Tam Ryvora, laterJoins, Resistance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterJoins Context triple: [Tam Ryvora, laterJoins, Resistance]
-
A.
hasPlayerWhoLaterJoined
Indicates that an entity has a player associated with it who, at some later time, joined another specified entity or group.
-
B.
laterMember
Indicates that one entity became a member of a group or organization at a later time than another entity.
-
C.
laterAttends
Indicates that one entity attends an event or place at a time later than another referenced attendance.
-
D.
laterLeaves
Indicates that one entity departs or leaves at a time that is later than the departure time of another entity.
-
E.
joins
chosen
Indicates that one entity becomes a member or part of another entity, typically by entering into an organization, group, or association.
- 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_69f07cb8033c8190b8807e219a14333d |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69fe30bc64308190b603ff1b30c2aeee |
completed | May 8, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69fe2f7175b081908dd61e1513620bbe |
completed | May 8, 2026, 6:46 p.m. |
Created at: April 28, 2026, noon