Triple
T31516399
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Riri Williams |
E804083
|
entity |
| Predicate | usesTechnologyBasedOn |
P76504
|
FINISHED |
| Object | Iron Man armor |
—
|
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: Iron Man armor | Statement: [Riri Williams, usesTechnologyBasedOn, Iron Man armor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesTechnologyBasedOn Context triple: [Riri Williams, usesTechnologyBasedOn, Iron Man armor]
-
A.
technologyUsedBy
chosen
Indicates that a particular technology is employed or utilized by a specified entity.
-
B.
technologyUsedIn
Indicates that a particular technology is employed or applied within a specific process, product, context, or domain.
-
C.
usesTechnologyInStory
Indicates that an entity incorporates or employs a particular technology within the context of a narrative or story.
-
D.
technologyUsedFor
Indicates that a particular technology is employed or applied to accomplish, support, or enable a specific purpose, task, or function.
-
E.
technologyUse
Indicates the use or application of a particular technology by an entity to perform an action or achieve a purpose.
- 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_69f348ceb0a48190ae7feca263b6296c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f7805ce6208190ac6dbd9c97989978 |
completed | May 3, 2026, 5:05 p.m. |
| PD | Predicate disambiguation | batch_69f77956ec648190ba4fb7e9d83fd107 |
completed | May 3, 2026, 4:35 p.m. |
Created at: April 30, 2026, 9:53 p.m.