Triple
T203511
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Bank Note |
E4558
|
entity |
| Predicate | obverseLanguage |
P3681
|
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: [National Bank Note, obverseLanguage, English]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: obverseLanguage Context triple: [National Bank Note, obverseLanguage, English]
-
A.
presentedInLanguage
chosen
Indicates that something (such as content, information, or a work) is expressed or made available using a particular language.
-
B.
emblemLanguage
Indicates that an emblem (such as a symbol or logo) is associated with or presented in a particular language.
-
C.
reverseInscription
Indicates that one entity is inscribed as the reverse or mirror image of another entity’s inscription.
-
D.
isLanguageOf
Indicates that a particular language is used as the official or primary language associated with a given entity (such as a person, document, or region).
-
E.
originalPublicationLanguageVariant
Indicates that one language is a specific variant or version of the language in which a work was originally published.
- 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_69a25737567c81908f9c505300239181 |
completed | Feb. 28, 2026, 2:47 a.m. |
| NER | Named-entity recognition | batch_69a25f46b4f081909e5ee3718109a71f |
completed | Feb. 28, 2026, 3:21 a.m. |
| PD | Predicate disambiguation | batch_69a25b4b42ec8190bef16bbbdd30a742 |
completed | Feb. 28, 2026, 3:04 a.m. |
Created at: Feb. 28, 2026, 2:51 a.m.