Triple
T22531237
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Criminologist |
E557040
|
entity |
| Predicate | addressesAudienceDirectly |
P92295
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [The Criminologist, addressesAudienceDirectly, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: addressesAudienceDirectly Context triple: [The Criminologist, addressesAudienceDirectly, true]
-
A.
relatesToAudience
Indicates a general relationship or relevance between something and a particular audience or group of recipients.
-
B.
intendedAudienceInteraction
chosen
Indicates that one entity is the target group or audience with whom another entity is meant to interact or engage.
-
C.
hasAudienceReach
Indicates the extent or scope of people or groups that are exposed to, can access, or are targeted by a particular entity, message, or activity.
-
D.
audienceOrientation
Indicates how something is directed, tailored, or positioned with respect to a particular audience or group of recipients.
-
E.
relationshipToAudience
Indicates the nature or type of connection an entity has with a specified audience, such as role, stance, or relevance.
- 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_69e11e57483c8190b0887c4f8ff26446 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15ed6734881908abbbee477dfab98 |
completed | April 29, 2026, 1:28 a.m. |
| PD | Predicate disambiguation | batch_69e898c864148190a3f5feec7967d49c |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:51 p.m.