Triple
T30711804
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Medusa |
E781913
|
entity |
| Predicate | exposedByCharacter |
P170053
|
FINISHED |
| Object | Jason Bourne |
—
|
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: Jason Bourne | Statement: [Medusa, exposedByCharacter, Jason Bourne]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exposedByCharacter Context triple: [Medusa, exposedByCharacter, Jason Bourne]
-
A.
analyzedByCharacter
Indicates that something (such as an event, object, or situation) is examined, interpreted, or evaluated by a particular character.
-
B.
explainedByCharacter
Indicates that something (such as an event, situation, or piece of information) is explained or clarified by a particular character.
-
C.
exploitedByCharacter
Indicates that a character takes unfair advantage of, manipulates, or otherwise uses another entity for their own benefit.
-
D.
experiencedByCharacter
Indicates that a particular event, situation, or emotion is undergone or lived through by a specific character.
-
E.
usedByCharacter
Indicates that something (such as an item, ability, or resource) is utilized or employed by a particular character.
- F. None of above. chosen
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_69f224acd24481908ed5f96f0d69b5dd |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f68c1efe608190a382d57a3aa3f542 |
completed | May 2, 2026, 11:43 p.m. |
| PD | Predicate disambiguation | batch_69f6861170d08190bb98be609d436f84 |
completed | May 2, 2026, 11:17 p.m. |
| PDg | Predicate description generation | batch_69f688034580819086a0f9100645f8ba |
completed | May 2, 2026, 11:25 p.m. |
Created at: April 29, 2026, 8:35 p.m.