Triple
T34999797
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mr. Wakem |
E1009639
|
entity |
| Predicate | legalOpponentOf |
P44728
|
FINISHED |
| Object | Mr. Tulliver |
—
|
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: Mr. Tulliver | Statement: [Mr. Wakem, legalOpponentOf, Mr. Tulliver]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalOpponentOf Context triple: [Mr. Wakem, legalOpponentOf, Mr. Tulliver]
-
A.
opponentInCase
chosen
Indicates that two parties are on opposing sides in the same legal case or proceeding.
-
B.
legalStrugglePartner
Indicates that two entities are engaged together as opposing or allied parties in a legal conflict or dispute.
-
C.
lawPartnerOf
Indicates a professional relationship in which two individuals are partners in the same law firm or legal practice.
-
D.
opposingParticipants
Indicates that the related entities are participants positioned in opposition to each other within the same interaction, event, or context.
-
E.
judicialPartner
Indicates a formal partnership or collaborative relationship between entities within a judicial or court-related context.
- 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_69f76dcb716881909f75e4fd60ab2284 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ff7eb7189c81909a8f73fbc4c48e02 |
completed | May 9, 2026, 6:36 p.m. |
| PD | Predicate disambiguation | batch_69ff7e54e11081908fb5ce10c5aa7b53 |
completed | May 9, 2026, 6:35 p.m. |
Created at: May 3, 2026, 4:01 p.m.