Triple
T4852409
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tamar |
E108446
|
entity |
| Predicate | locationOfAssault |
P20435
|
FINISHED |
| Object | Amnon’s house |
—
|
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: Amnon’s house | Statement: [Tamar, locationOfAssault, Amnon’s house]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationOfAssault Context triple: [Tamar, locationOfAssault, Amnon’s house]
-
A.
assaultedBy
Indicates that an entity has been attacked or subjected to violent physical aggression by another entity.
-
B.
assassinationAttemptLocation
Indicates the place where an attempted assassination occurred or was intended to occur.
-
C.
allegedShooterLocation
Indicates the place where a person is claimed or reported to have carried out a shooting.
-
D.
attackedIn
Indicates that one entity carried out an attack in the location, context, or time frame specified by another entity or value.
-
E.
notableAttackLocation
chosen
Indicates the specific place where a significant or notable attack occurred in relation to the subject.
- 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_69bd440a89548190a5f14ba6da6b97dc |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6ddd17d881909f7731ff2b460e83 |
completed | March 20, 2026, 3:55 p.m. |
| PD | Predicate disambiguation | batch_69bd6c2557388190a2d15571bacd24f3 |
completed | March 20, 2026, 3:47 p.m. |
Created at: March 20, 2026, 1:26 p.m.