Triple
T35350460
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alicia Masters |
E1020863
|
entity |
| Predicate | supportsHero |
P48343
|
FINISHED |
| Object | Fantastic Four |
E219137
|
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: Fantastic Four | Statement: [Alicia Masters, supportsHero, Fantastic Four]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsHero Context triple: [Alicia Masters, supportsHero, Fantastic Four]
-
A.
supportCharacter
Indicates that one entity provides assistance, backing, or reinforcement to another entity in performing an action or fulfilling a role.
-
B.
supportedByCharacter
chosen
Indicates that an entity receives backing, assistance, or endorsement from a specific character.
-
C.
targetsHeroes
Indicates that an entity directs attacks, actions, or effects specifically toward hero characters.
-
D.
supportsNPCs
Indicates that an entity provides functionality or compatibility for non-player characters (NPCs) within a system or environment.
-
E.
includesHeroes
Indicates that something (such as a work, group, or collection) contains or features one or more heroes as part of it.
- 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_69f76decd95c8190ae428f6a19d535de |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a384a17a34c8190915cf4f0778d6a7d |
completed | June 21, 2026, 8:31 p.m. |
| PD | Predicate disambiguation | batch_6a037a0324d08190ac5b610cc0f6a38c |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:03 p.m.