Triple
T36965753
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Portrait |
E914422
|
entity |
| Predicate | performerKnownFor |
P131071
|
FINISHED |
| Object | Wonder Woman (TV series) |
—
|
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 (TV series) | Statement: [Portrait, performerKnownFor, Wonder Woman (TV series)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performerKnownFor Context triple: [Portrait, performerKnownFor, Wonder Woman (TV series)]
-
A.
nowKnownFor
Indicates that an entity is currently recognized or notable for a particular role, attribute, achievement, or association.
-
B.
alsoKnownFor
Indicates that an entity is additionally recognized or noted for another work, role, achievement, or characteristic beyond its primary association.
-
C.
creatorKnownFor
Indicates that a creator is especially recognized or notable for a particular work, contribution, or achievement.
-
D.
performerOn
Indicates that an entity serves as the performer or executing agent of an action, event, or work associated with another entity.
-
E.
actorKnownFor
chosen
Indicates that an actor is widely recognized or notable for a particular work, role, or contribution.
- 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_69f76e8c498c8190b2842db80aea8b3b |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ff2fbae9b48190847eefa1c227d43e |
completed | May 9, 2026, 12:59 p.m. |
| PD | Predicate disambiguation | batch_69ff2f2218048190a32224a648182b5d |
completed | May 9, 2026, 12:57 p.m. |
Created at: May 3, 2026, 4:14 p.m.