Triple
T29078656
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gateway City |
E733912
|
entity |
| Predicate | primaryAssociatedSuperhero |
P131662
|
FINISHED |
| Object | Wonder Woman |
—
|
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: Wonder Woman | Statement: [Gateway City, primaryAssociatedSuperhero, Wonder Woman]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryAssociatedSuperhero Context triple: [Gateway City, primaryAssociatedSuperhero, Wonder Woman]
-
A.
associatedWithSuperhero
chosen
Indicates that one entity has a notable connection, link, or involvement with a superhero entity.
-
B.
associatedWithSuperheroIdentity
Indicates that an entity has a connection or linkage to a particular superhero identity, such as being or representing that superhero persona.
-
C.
featuresCharacterWithSuperpowers
Indicates that the subject includes or portrays a character who possesses superhuman abilities or powers.
-
D.
daughterSuperheroAlias
Indicates that one entity is the superhero alias or identity used by the daughter of another entity.
-
E.
associatedEpicHero
Indicates a relationship where one entity is linked to, or thematically connected with, a particular epic hero.
- F. None of above.
Provenance (3 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_69f05b0c0f28819086eae6e84f2ae472 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_6a00b34364448190b8c9948d5a24d845 |
completed | May 10, 2026, 4:33 p.m. |
| PD | Predicate disambiguation | batch_6a00b2e4f13c819081bac7d763c414ad |
completed | May 10, 2026, 4:31 p.m. |
Created at: April 28, 2026, 10:51 a.m.