Triple
T22049746
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ministers of State (Singapore) |
E544851
|
entity |
| Predicate | languageUsedInTitle |
P58450
|
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: [Ministers of State (Singapore), languageUsedInTitle, English]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageUsedInTitle Context triple: [Ministers of State (Singapore), languageUsedInTitle, English]
-
A.
languageUsedAs
Indicates that one language is employed in a specific role, function, or context relative to another entity or situation.
-
B.
languageName
Indicates the specific name assigned to a language in the relationship.
-
C.
languageOfTitleHolder
Indicates the language in which the title held by a given title holder is expressed or recorded.
-
D.
languagesUsed
chosen
Indicates that one entity uses, employs, or is expressed in one or more languages associated with the other entity.
-
E.
languageSpecifies
Indicates that one entity defines or constrains the syntax, semantics, or usage rules that govern how another language or linguistic system is expressed or interpreted.
- 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_69e11e32445c8190ab97089b48a130bb |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f128323fb08190b9592fd08a96cba0 |
completed | April 28, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69e6f643ca74819083e8ab78e843f243 |
completed | April 21, 2026, 4 a.m. |
Created at: April 16, 2026, 8:26 p.m.