Triple
T30119139
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clarissa MacDougall |
E765507
|
entity |
| Predicate | partnerInCombatAndLifeOf |
P140399
|
FINISHED |
| Object | Kimball Kinnison |
—
|
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: Kimball Kinnison | Statement: [Clarissa MacDougall, partnerInCombatAndLifeOf, Kimball Kinnison]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partnerInCombatAndLifeOf Context triple: [Clarissa MacDougall, partnerInCombatAndLifeOf, Kimball Kinnison]
-
A.
partnerInBattle
chosen
Indicates that two entities are allied or cooperate as partners in the same battle or combat engagement.
-
B.
partnerInMyth
Indicates a mythological relationship in which two entities are partners or companions within the same myth or mythic narrative.
-
C.
partnerInConflictWith
Indicates that two entities are engaged as opposing partners or sides within the same conflict or dispute.
-
D.
partnerInLoveTeam
Indicates that two entities are teammates who are also partners in a romantic or love-based relationship.
-
E.
partnerInLifeAndPracticeWith
Indicates a relationship where two individuals are both life partners and professional collaborators in their work or practice.
- 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_69f2247716748190ae4f16998f49ddf1 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6b2a65c7c8190ac40f1466ceadefc |
completed | May 3, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f6b14d7d508190bc7d4c89dfba4a32 |
completed | May 3, 2026, 2:22 a.m. |
Created at: April 29, 2026, 7:12 p.m.