Triple
T14476854
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | What Where |
E358994
|
entity |
| Predicate | audienceInterpretation |
P67724
|
FINISHED |
| Object | open-ended |
—
|
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: open-ended | Statement: [What Where, audienceInterpretation, open-ended]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: audienceInterpretation Context triple: [What Where, audienceInterpretation, open-ended]
-
A.
intendedInterpretation
chosen
Indicates that one entity is meant to be understood or interpreted in a particular way, sense, or meaning relative to another.
-
B.
interpretiveRole
Indicates that one entity serves as an interpretive function or perspective through which another entity is understood, explained, or given meaning.
-
C.
audienceScale
Indicates the relative size or reach of the audience associated with an entity, event, or communication.
-
D.
audienceRole
Indicates the role or function an entity has as part of an audience in relation to another entity or event.
-
E.
audienceOrientation
Indicates how something is directed, tailored, or positioned with respect to a particular audience or group of recipients.
- 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_69d827966698819082e140837737501d |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de9248edb48190a74eb032aeaac027 |
completed | April 14, 2026, 7:15 p.m. |
| PD | Predicate disambiguation | batch_69de5c42bd3c81909a62acf30cc24d1e |
completed | April 14, 2026, 3:24 p.m. |
Created at: April 10, 2026, 1:20 a.m.