Triple
T19268493
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | George (Gosford Park) |
E481852
|
entity |
| Predicate | employedByInStory |
P93486
|
FINISHED |
| Object | Lord and Lady McCordle household |
—
|
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: Lord and Lady McCordle household | Statement: [George (Gosford Park), employedByInStory, Lord and Lady McCordle household]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: employedByInStory Context triple: [George (Gosford Park), employedByInStory, Lord and Lady McCordle household]
-
A.
employerInPlot
chosen
Indicates that one entity serves as the employer of another within the context of a specific plot or storyline.
-
B.
employedTo
Indicates that one entity is hired or engaged to perform work, services, or duties for another entity.
-
C.
workBasedOnThisCharacter
Indicates that a creative work is based on, inspired by, or derived from the referenced character.
-
D.
employerInUniverse
Indicates that one entity serves as the employer of another within a specified universe, context, or world.
-
E.
workAt
Indicates that an entity is employed by or performs work for a particular organization, company, or place.
- 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_69d8e8ce54cc8190998418ff1f66ef28 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fbb68d0c819083ba0ce680dd7d99 |
completed | April 20, 2026, 10:11 a.m. |
| PD | Predicate disambiguation | batch_69e4dd07a7208190afcd51ba1dc87c33 |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:29 p.m.