Triple
T34726390
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Guardsman |
E1001079
|
entity |
| Predicate | languageOfNotableProduction |
P115202
|
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: [The Guardsman, languageOfNotableProduction, English]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageOfNotableProduction Context triple: [The Guardsman, languageOfNotableProduction, English]
-
A.
areSpokenIn
Indicates that a particular language is used as a spoken means of communication within a specified region, community, or context.
-
B.
workLanguageOfTitle
chosen
Indicates the language in which a specific work or title is expressed or written.
-
C.
notableLanguageOfWorks
Indicates that a particular language is especially prominent or significant among the works created by an entity.
-
D.
notableEnglishProduction
Indicates that an entity has a significant or well-known production (such as a performance, adaptation, or staging) specifically in the English language.
-
E.
filmedInLanguage
Indicates that a film or video work was originally recorded using a particular spoken or signed 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_69f76daeb6e48190a4c9a6b0edc80f72 |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_6a008098e5dc8190b7ccad8bab780343 |
completed | May 10, 2026, 12:56 p.m. |
| PD | Predicate disambiguation | batch_6a008037267c8190990225a6ff0b3694 |
completed | May 10, 2026, 12:55 p.m. |
Created at: May 3, 2026, 3:59 p.m.