Triple
T25953408
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rupert Falkner |
E654025
|
entity |
| Predicate | hasSurnameTitleWork |
P160063
|
FINISHED |
| Object | Falkner |
—
|
NE NERFINISHED |
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: Falkner | Statement: [Rupert Falkner, hasSurnameTitleWork, Falkner]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSurnameTitleWork Context triple: [Rupert Falkner, hasSurnameTitleWork, Falkner]
-
A.
hasTitleWork
Indicates that an entity is associated with a specific work by its title (i.e., the entity has or bears that work’s title).
-
B.
hasFullNameInWork
Indicates that an entity is referred to by a specific full name within a particular work or publication.
-
C.
hasWorkTitleVariant
chosen
Indicates that an entity has an alternative or variant form of its work title, such as a different wording, spelling, or language version of the same title.
-
D.
hasGivenNameInWork
Indicates that a work specifies or uses a particular given (first) name for an entity or character.
-
E.
hasGivenNameInTitle
Indicates that the given name of an entity appears within the title of another entity.
- 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_69e7ab40ac788190a771bc499eb1ae5f |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6d0d46aec819091edf97324d793ac |
completed | May 3, 2026, 4:36 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe2183481908ae4e85a59c66f69 |
completed | May 3, 2026, 4:32 a.m. |
Created at: April 22, 2026, 8:44 a.m.