Triple
T21357121
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paul Federn |
E526660
|
entity |
| Predicate | laterWorkLanguage |
P45484
|
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: [Paul Federn, laterWorkLanguage, English]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterWorkLanguage Context triple: [Paul Federn, laterWorkLanguage, English]
-
A.
usesWorkingLanguagesOf
Indicates that one entity employs or operates using the working languages associated with another entity.
-
B.
primaryLanguageInWork
Indicates that a specified language is the main or predominant language used within a particular work (such as a book, film, or document).
-
C.
hasWorkedInLanguage
chosen
Indicates that an entity has performed work or professional activities using a particular language.
-
D.
workLanguageVariant
Indicates that one language variant of a work is related to another version of the same work, typically differing by language or localization.
-
E.
laterOfficialLanguage
Indicates that one language became an official language of an entity at a later time than another 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_69e0b51d8a308190b09113b3b3f9bc15 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e8afa1a9b0819083a5a8f34c49d409 |
completed | April 22, 2026, 11:23 a.m. |
| PD | Predicate disambiguation | batch_69e6162bbfc88190a3e75859941b2638 |
completed | April 20, 2026, 12:03 p.m. |
Created at: April 16, 2026, 5:07 p.m.