Triple
T35470809
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Christopher Drake |
E1025200
|
entity |
| Predicate | notableCharacterScored |
P107871
|
FINISHED |
| Object | Batman |
E74786
|
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: Batman | Statement: [Christopher Drake, notableCharacterScored, Batman]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableCharacterScored Context triple: [Christopher Drake, notableCharacterScored, Batman]
-
A.
hasNotableScore
Indicates that an entity is associated with a score or rating considered significant or noteworthy in its context.
-
B.
scoredForCharacter
chosen
Indicates that one entity achieved or recorded a score on behalf of, or associated with, a particular character.
-
C.
notableCharacterSport
Indicates that a notable character is associated with, participates in, or is prominently linked to a particular sport.
-
D.
notableRunnerScored
Indicates that a runner who is considered notable successfully scored (e.g., a run or point) in the relevant event or context.
-
E.
notableLeagueCharacteristic
Indicates that a particular characteristic is especially prominent or defining for a given league.
- 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_69f76dfadba0819083456aadcd6864ea |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3840381efc8190a1fefc74c15050a5 |
completed | June 21, 2026, 7:49 p.m. |
| PD | Predicate disambiguation | batch_6a037a0324d08190ac5b610cc0f6a38c |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:04 p.m.