Triple
T3859953
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Anderson Tapes |
E90109
|
entity |
| Predicate | hasHeistType |
P20949
|
FINISHED |
| Object | apartment building robbery |
—
|
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: apartment building robbery | Statement: [The Anderson Tapes, hasHeistType, apartment building robbery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHeistType Context triple: [The Anderson Tapes, hasHeistType, apartment building robbery]
-
A.
haveType
Indicates that an entity belongs to or is classified under a specified type or category.
-
B.
hasTrickType
Indicates that an entity (such as a trick or maneuver) is associated with a specific type or category of trick.
-
C.
hasTypeOfInsignia
Indicates that an entity bears or is associated with a specific kind or category of insignia.
-
D.
hasActivityType
chosen
Indicates the specific kind or category of activity associated with an entity or event.
-
E.
hasStratotype
Indicates that one entity serves as the designated standard or reference example (stratotype) for defining the stratigraphic characteristics of another entity.
- 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_69aed95b3c088190a8f85d19e6070599 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeec1ff39c8190b83a88abd840a0e3 |
completed | March 9, 2026, 3:49 p.m. |
| PD | Predicate disambiguation | batch_69aee752c8a48190a670f73ed0bf1e61 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:19 p.m.