Triple
T10118898
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sacrilege |
E223232
|
entity |
| Predicate | intendedAudienceInteraction |
P92295
|
FINISHED |
| Object | jumping |
—
|
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: jumping | Statement: [Sacrilege, intendedAudienceInteraction, jumping]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendedAudienceInteraction Context triple: [Sacrilege, intendedAudienceInteraction, jumping]
-
A.
interactionWithHumans
Indicates a relationship where an entity engages in some form of contact, communication, or mutual influence with humans.
-
B.
relatesToAudience
Indicates a general relationship or relevance between something and a particular audience or group of recipients.
-
C.
seeksEngagementWith
Indicates an entity’s active effort or intention to initiate or maintain interaction, involvement, or responsive connection with another entity.
-
D.
engagementOf
Indicates a relationship where an engagement, commitment, or formal involvement is associated with or attributed to a specific entity.
-
E.
interactive
Indicates that one entity engages in reciprocal or two-way communication or action with another entity.
- 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_69ca8422047c81909d66b717b8b18cf3 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cdd26460a4819093a3b239d97c3e3d |
completed | April 2, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_69cd4b9ed7e48190aa132ef8a69b49f9 |
completed | April 1, 2026, 4:45 p.m. |
| PDg | Predicate description generation | batch_69cd4f8f869c8190a82ad040993e0244 |
completed | April 1, 2026, 5:02 p.m. |
Created at: March 30, 2026, 9:04 p.m.