Triple
T29848467
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | London European Parliament constituency |
E757996
|
entity |
| Predicate | languageUsedInOfficialMaterial |
P19280
|
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: [London European Parliament constituency, languageUsedInOfficialMaterial, English]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageUsedInOfficialMaterial Context triple: [London European Parliament constituency, languageUsedInOfficialMaterial, English]
-
A.
officialLanguageOfProgramMaterials
Indicates the language officially used in the materials or documentation of a program.
-
B.
languageOfOfficialAnnouncements
Indicates the language used for formal or official public announcements issued by an authority.
-
C.
languageOfOfficialEditions
chosen
Indicates the language in which the official editions or versions of a work, document, or publication are produced or authorized.
-
D.
shareOfficialLanguage
Indicates that two entities have at least one official language in common.
-
E.
hasLanguageOfficial
Indicates that a language holds official status within a given entity, such as a country, region, or organization.
- 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_69f2245a82cc8190a387e7d0118d710b |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69fed6da0390819096b88ef4714b144e |
completed | May 9, 2026, 6:40 a.m. |
| PD | Predicate disambiguation | batch_69fed53517d081909966f31707625f1a |
completed | May 9, 2026, 6:33 a.m. |
Created at: April 29, 2026, 5:42 p.m.