Triple
T34343751
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Bourne Supremacy |
E881370
|
entity |
| Predicate | notableCharacterAlias |
P138329
|
FINISHED |
| Object | Jason Bourne |
E39808
|
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: Jason Bourne | Statement: [The Bourne Supremacy, notableCharacterAlias, Jason Bourne]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableCharacterAlias Context triple: [The Bourne Supremacy, notableCharacterAlias, Jason Bourne]
-
A.
characterAlias
Indicates that one character is known or referred to by an alternative name or alias.
-
B.
notableCharacterName
chosen
Indicates that the subject has a notable or significant character whose name is given by the object.
-
C.
hasFictionalAlias
Indicates that an entity is known by an alternative name or identity within a fictional context.
-
D.
alsoKnownAs
Indicates that one entity is an alternative name, alias, or designation for another entity.
-
E.
associatedWithCharacterAlias
Indicates that one entity is linked to or connected with an alternative name or alias used for a particular character.
- 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_69f349bc55e881908c8e338ef76b0043 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3729c656ac8190a31bc4528985ccaf |
completed | June 21, 2026, 12:01 a.m. |
| PD | Predicate disambiguation | batch_6a0379fbe4a08190bfe65ebd141164e9 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:58 a.m.