Triple
T25265967
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harambe |
E633429
|
entity |
| Predicate | performerSpouseOfInfluence |
P33561
|
FINISHED |
| Object | Bob Marley |
E30748
|
NE FINISHED |
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: Bob Marley | Statement: [Harambe, performerSpouseOfInfluence, Bob Marley]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performerSpouseOfInfluence Context triple: [Harambe, performerSpouseOfInfluence, Bob Marley]
-
A.
genreAssociatedWithSpouse
Indicates that a particular genre is associated with, or characterizes, the spouse of the referenced entity.
-
B.
spouseAssociatedWith
chosen
Indicates a marital or spousal relationship or close association between two entities.
-
C.
hasPublicFigureSpouse
Indicates that a person’s spouse is a public figure, such as a celebrity, politician, or other widely recognized individual.
-
D.
spouseNotableFor
Indicates that a person's spouse is recognized or distinguished for a particular achievement, role, or characteristic.
-
E.
sometimesSpouseOf
Indicates that two entities are occasionally, but not consistently or permanently, in a spousal relationship with each other.
- F. None of above.
Provenance (4 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_69e75a92f48881909974ff9c11150a2e |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f60c3b09488190ade1b69ff7f0df0e |
completed | May 2, 2026, 2:37 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a10ad433b548190b695a902c9b1c964 |
completed | May 22, 2026, 7:23 p.m. |
| PD | Predicate disambiguation | batch_69f60b8461ac81908c5bd3d73eed59f4 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 21, 2026, 1:16 p.m.