Triple
T27041001
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asia Society Award for Cultural Achievement |
E684485
|
entity |
| Predicate | hasLanguageOfActivities |
P35567
|
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: [Asia Society Award for Cultural Achievement, hasLanguageOfActivities, English]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLanguageOfActivities Context triple: [Asia Society Award for Cultural Achievement, hasLanguageOfActivities, English]
-
A.
hasLanguageOfMission
Indicates that an entity (such as a mission or project) is associated with a specific language used for its communication, documentation, or operation.
-
B.
usesWorkingLanguagesOf
Indicates that one entity employs or operates using the working languages associated with another entity.
-
C.
hasLanguages
chosen
Indicates that an entity is associated with one or more languages it uses, supports, or is expressed in.
-
D.
hasLanguageOn
Indicates that an entity uses or is associated with a particular language in a specific context, medium, or location.
-
E.
hasOwnLanguage
Indicates that an entity possesses or uses a distinct language of its own.
- 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_69ef148193c48190bb1a0cfae6a407c4 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f7764ab1fc81909f9348db87bd7692 |
completed | May 3, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69f76905d9c88190b1ee810bc9ab644f |
completed | May 3, 2026, 3:25 p.m. |
Created at: April 27, 2026, 8:05 a.m.