Triple
T19048550
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clearing |
E466197
|
entity |
| Predicate | workTitleLanguageNote |
P24259
|
FINISHED |
| Object | English title used internationally |
—
|
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 title used internationally | Statement: [Clearing, workTitleLanguageNote, English title used internationally]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workTitleLanguageNote Context triple: [Clearing, workTitleLanguageNote, English title used internationally]
-
A.
workTitle
chosen
Indicates the formal title or name of a work (such as a book, artwork, or composition) associated with an entity.
-
B.
workLanguageOfTitle
Indicates the language in which a specific work or title is expressed or written.
-
C.
workTitleType
Indicates the specific category or type of a work’s title (e.g., main title, alternative title, translated title) in relation to that work.
-
D.
workTitleWithOpus
Indicates that a work’s title is associated with a specific opus number designation.
-
E.
officialTitleInLanguage
Indicates that an entity’s official title or designation is expressed in a specified language.
- 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_69d8dd040fb881909af2a964f65ad208 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d8062ea481908cf3fcb790a74956 |
completed | April 20, 2026, 7:38 a.m. |
| PD | Predicate disambiguation | batch_69e4b99633c8819097988608c278ecf8 |
completed | April 19, 2026, 11:16 a.m. |
Created at: April 10, 2026, 12:03 p.m.