Triple
T19527119
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Steve Lacey |
E488552
|
entity |
| Predicate | hasPastAs |
P99136
|
FINISHED |
| Object | bank robber |
—
|
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: bank robber | Statement: [Steve Lacey, hasPastAs, bank robber]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPastAs Context triple: [Steve Lacey, hasPastAs, bank robber]
-
A.
hasHad
Indicates that an entity previously experienced, possessed, or was involved in something at some point in the past.
-
B.
hasHistoryIn
chosen
Indicates that an entity has a past involvement, presence, or record of activity within a particular domain, context, or location.
-
C.
hasOwnerInThePast
Indicates that an entity was owned by another entity at some time in the past, but not necessarily in the present.
-
D.
hasMet
Indicates that one entity has encountered or come into contact with another entity at least once.
-
E.
hasHistoryOf
Indicates that an entity has a documented prior occurrence or background of a specified condition, event, or state.
- 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_69d8e8da8bec819081f400199491ccc3 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6363c2660819093a6b9a444ca0ad4 |
completed | April 20, 2026, 2:20 p.m. |
| PD | Predicate disambiguation | batch_69e514c9c00481909b76bda67957e58b |
completed | April 19, 2026, 5:45 p.m. |
Created at: April 10, 2026, 1:41 p.m.