Triple
T13278995
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IEEE Visualization Best Paper Award |
E316267
|
entity |
| Predicate | languageOfConference |
P15031
|
FINISHED |
| Object | English |
—
|
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: English | Statement: [IEEE Visualization Best Paper Award, languageOfConference, English]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageOfConference Context triple: [IEEE Visualization Best Paper Award, languageOfConference, English]
-
A.
languageOfEvent
chosen
Indicates the language in which an event is conducted, presented, or communicated.
-
B.
languageOfCommunications
Indicates that a specified language is used as the medium for communications associated with an entity or interaction.
-
C.
languageOfVenue
Indicates the language primarily used or officially designated for communication at a given venue.
-
D.
languageOfExpression
Indicates that a particular language is used as the medium or form in which an expression (such as a text, utterance, or work) is realized.
-
E.
languageDiscussedIn
Indicates that a particular language is the topic of discussion within a specified context, source, or discourse.
- 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_69d806b349908190a9a61dd9323bf153 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99cfdc9388190af1fdd3cd4717bd8 |
completed | April 11, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69d98f6535688190a5a4549b7be2d611 |
completed | April 11, 2026, 12:01 a.m. |
Created at: April 9, 2026, 9:26 p.m.