Triple
T31903111
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2008 Mumbai attacks |
E814475
|
entity |
| Predicate | targetedType |
P168669
|
FINISHED |
| Object | luxury hotels |
—
|
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: luxury hotels | Statement: [2008 Mumbai attacks, targetedType, luxury hotels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetedType Context triple: [2008 Mumbai attacks, targetedType, luxury hotels]
-
A.
typicalTargetType
Indicates the usual or most common type or category of entity that serves as the target or recipient in a given relationship or action.
-
B.
primaryTargetType
Indicates the main category or type of entity that is the principal focus or intended recipient of an action, effect, or operation.
-
C.
attackTargetType
chosen
Indicates the type or category of target that an attack is directed against.
-
D.
notableTargetType
Indicates that the subject is notable or significant specifically in relation to entities of the given target type.
-
E.
targetedBecauseOf
Indicates that one entity is made a target of an action, harm, or scrutiny specifically due to possessing a particular attribute, identity, or characteristic.
- 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_69f348f04d7881909537fc9e7cbc670e |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fdb04ed81c8190b8feea90c1c785a6 |
completed | May 8, 2026, 9:43 a.m. |
| PD | Predicate disambiguation | batch_69fda9d6c5148190a63205b6d9b0a1b4 |
completed | May 8, 2026, 9:16 a.m. |
Created at: May 1, 2026, midnight