Triple
T33610511
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mortal Man |
E860974
|
entity |
| Predicate | featuresPosthumousInterviewWith |
P40000
|
FINISHED |
| Object | Tupac Shakur |
E27310
|
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: Tupac Shakur | Statement: [Mortal Man, featuresPosthumousInterviewWith, Tupac Shakur]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresPosthumousInterviewWith Context triple: [Mortal Man, featuresPosthumousInterviewWith, Tupac Shakur]
-
A.
usesInterviews
Indicates that one entity employs interviews as a method or tool in relation to another entity or process.
-
B.
interviewedBy
chosen
Indicates that an entity is the subject of an interview conducted by another entity.
-
C.
gaveInterviewsAbout
Indicates that an entity conducted interviews whose subject or topic was another specified entity.
-
D.
interviewSeries
Indicates a relationship where multiple interviews are organized as a connected, sequential series under a common theme or context.
-
E.
interviewees
Indicates that certain entities are the subjects or participants being questioned or evaluated in an interview process.
- 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_69f3498037c88190a4500f002b5540e0 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a01d9ca07b88190b4ad70b6336447b6 |
completed | May 11, 2026, 1:29 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a36119dbe8c8190aca70b690176b802 |
completed | June 20, 2026, 4:05 a.m. |
| PD | Predicate disambiguation | batch_6a01d807c3048190b79f0b6b933dd3b7 |
completed | May 11, 2026, 1:22 p.m. |
Created at: May 1, 2026, 1:41 a.m.