Triple
T27635267
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | killing of Philip Barton Key II |
E696452
|
entity |
| Predicate | hasPublicity |
P168950
|
FINISHED |
| Object | highly publicized |
—
|
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: highly publicized | Statement: [killing of Philip Barton Key II, hasPublicity, highly publicized]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPublicity Context triple: [killing of Philip Barton Key II, hasPublicity, highly publicized]
-
A.
hasPublicPerception
Indicates that an entity is associated with a particular way it is viewed, judged, or regarded by the general public or society.
-
B.
hasPublicityStunt
Indicates that an entity engages in or is associated with a planned publicity stunt intended to attract public attention.
-
C.
hasPublic
Indicates that an entity is accessible or visible to the general public rather than being private or restricted.
-
D.
hasPublicFigure
Indicates that an entity is associated with or characterized by a specific public figure, such as a celebrity, politician, or other widely recognized individual.
-
E.
sessionPublicity
Indicates that information about a session is made publicly accessible or promoted to a general audience.
- F. None of above. chosen
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_69ef5909f3848190805f35b76833e722 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f67866e9248190b7ba218f9ca2ae8d |
completed | May 2, 2026, 10:19 p.m. |
| PD | Predicate disambiguation | batch_69f675fd59608190b246383435e68fce |
completed | May 2, 2026, 10:09 p.m. |
| PDg | Predicate description generation | batch_69f676c35f3481909b9ba18a5662d6ce |
completed | May 2, 2026, 10:12 p.m. |
Created at: April 27, 2026, 2:23 p.m.