Triple
T34769453
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A Real Hero |
E1002320
|
entity |
| Predicate | notableUseInWork |
P10343
|
FINISHED |
| Object | Drive |
E1436821
|
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: Drive | Statement: [A Real Hero, notableUseInWork, Drive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableUseInWork Context triple: [A Real Hero, notableUseInWork, Drive]
-
A.
notableWorkUsed
Indicates that a particular notable work is utilized, referenced, or incorporated in relation to another entity or context.
-
B.
usedInWorkBy
Indicates that something (such as a method, material, or concept) is employed or incorporated within a work created by a particular agent or author.
-
C.
usedInWork
chosen
Indicates that something (such as a concept, method, material, or component) is employed or applied within a particular work, project, or creation.
-
D.
notableUse
Indicates that something is prominently or famously used by a particular entity, context, or for a specific purpose.
-
E.
notableFromWork
Indicates that an entity is notable or well-known specifically because of a particular work it created, contributed to, or is associated with.
- 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_69f76db20dac8190b1e8d0ca4dc1d59f |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3766398bc88190a4f5047116a7cb6b |
completed | June 21, 2026, 4:19 a.m. |
| PD | Predicate disambiguation | batch_6a0379fd7aac8190873077e63873aa72 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 3:59 p.m.