Triple
T17786201
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Collectors |
E444022
|
entity |
| Predicate | engagesAudienceAs |
P128911
|
FINISHED |
| Object | witness |
—
|
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: witness | Statement: [The Collectors, engagesAudienceAs, witness]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: engagesAudienceAs Context triple: [The Collectors, engagesAudienceAs, witness]
-
A.
attractsAudience
Indicates that an entity draws the interest or attention of people who choose to watch, listen to, or engage with it.
-
B.
intendedAudienceInteraction
Indicates that one entity is the target group or audience with whom another entity is meant to interact or engage.
-
C.
hasAudienceParticipation
Indicates that an event, performance, or activity involves direct participation or interaction from the audience.
-
D.
engagementOf
Indicates a relationship where an engagement, commitment, or formal involvement is associated with or attributed to a specific entity.
-
E.
seeksEngagementWith
Indicates an entity’s active effort or intention to initiate or maintain interaction, involvement, or responsive connection 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_69d8b9ef17708190bdf7e2adbf14ddc2 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e487938418819096016ad717b014e6 |
completed | April 19, 2026, 7:43 a.m. |
| PD | Predicate disambiguation | batch_69e3d8d8e538819084f1584426b41d5e |
completed | April 18, 2026, 7:17 p.m. |
| PDg | Predicate description generation | batch_69e3db7704588190a34a422421152173 |
completed | April 18, 2026, 7:28 p.m. |
Created at: April 10, 2026, 10:12 a.m.