Triple
T32031813
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harley Keener |
E817982
|
entity |
| Predicate | receivesFromTonyStark |
P4382
|
FINISHED |
| Object | upgraded workshop equipment |
—
|
LITERAL 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: upgraded workshop equipment | Statement: [Harley Keener, receivesFromTonyStark, upgraded workshop equipment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: receivesFromTonyStark Context triple: [Harley Keener, receivesFromTonyStark, upgraded workshop equipment]
-
A.
roleInTonyStarkLife
Indicates the specific role or significance an entity has in Tony Stark's life.
-
B.
receives
chosen
Indicates that one entity is the recipient of something (such as an object, message, or action) from another entity.
-
C.
recipientOf
Indicates that one entity is the receiver or beneficiary of something (such as an item, message, or action) from another entity.
-
D.
receivesAsRansom
Indicates that one entity accepts another entity as payment or exchange in a ransom situation.
-
E.
roleRelativeToBlackPanther
Indicates the specific narrative or functional role an entity has in relation to Black Panther (e.g., ally, enemy, family member, or other contextual position).
- 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_69f348fbc8148190b3c0f95d4772b153 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7221dc9a88190bb8194fcc29c42bc |
completed | May 3, 2026, 10:23 a.m. |
| PD | Predicate disambiguation | batch_69f72153a9188190b02adc84e1be4af8 |
completed | May 3, 2026, 10:20 a.m. |
Created at: May 1, 2026, 12:18 a.m.