Triple
T38593243
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tactical Visor |
E932501
|
entity |
| Predicate | associatedHeroRealName |
P155411
|
FINISHED |
| Object | Jack Morrison |
E932498
|
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: Jack Morrison | Statement: [Tactical Visor, associatedHeroRealName, Jack Morrison]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedHeroRealName Context triple: [Tactical Visor, associatedHeroRealName, Jack Morrison]
-
A.
titleCharacterRealName
chosen
Indicates that a character known by a title or alias has the specified real (personal) name.
-
B.
hasEponymousHero
Indicates that a work or narrative features a hero whose name is the same as, or gives its name to, the work itself.
-
C.
associatedWithSuperhero
Indicates that one entity has a notable connection, link, or involvement with a superhero entity.
-
D.
protagonistRealWorldName
Indicates that a character’s name in the real world (outside a fictional, virtual, or alternate setting) is associated with that character as the story’s protagonist.
-
E.
characterRealWorldCounterpart
Indicates that a fictional character is based on, inspired by, or directly corresponds to a specific real-world person.
- 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_69f76ec654d48190b421111cf26e54d9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a41fd5072348190bcbac7c8696df458 |
completed | June 29, 2026, 5:06 a.m. |
| PD | Predicate disambiguation | batch_6a037a2026248190b894436a578d79ac |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:32 p.m.