Triple
T30326939
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | In Praise of the Music of Language |
E771367
|
entity |
| Predicate | associatedWithMainTitleLanguage |
P87230
|
FINISHED |
| Object | French |
—
|
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: French | Statement: [In Praise of the Music of Language, associatedWithMainTitleLanguage, French]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithMainTitleLanguage Context triple: [In Praise of the Music of Language, associatedWithMainTitleLanguage, French]
-
A.
commonTitleLanguage
Indicates that two entities share the same language in which their titles are expressed.
-
B.
linkedToLanguage
chosen
Indicates that an entity has an association or connection with a specific language, such as being expressed in, related to, or dependent on that language.
-
C.
hasRelatedLanguage
Indicates that one language is related to another through shared linguistic origins, features, or classification.
-
D.
hasTitleInLanguage
Indicates that an entity has a specific title expressed in a particular language.
-
E.
hasMainLocale
Indicates that an entity’s primary or default locale (language and regional setting) is a specified locale.
- 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_69f22489ee8481909344649bfbb92e83 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e2fac0819089b522db3260028c |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 7:53 p.m.