Triple
T30613574
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tommy Lascelles (The Crown) |
E779252
|
entity |
| Predicate | servesAsAdvisorTo |
P36354
|
FINISHED |
| Object | King George VI (The Crown) |
—
|
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: King George VI (The Crown) | Statement: [Tommy Lascelles (The Crown), servesAsAdvisorTo, King George VI (The Crown)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesAsAdvisorTo Context triple: [Tommy Lascelles (The Crown), servesAsAdvisorTo, King George VI (The Crown)]
-
A.
advisorOf
chosen
Indicates that one entity serves as an advisor, providing guidance or counsel, to another entity.
-
B.
notableAdvisor
Indicates that one entity serves, or has served, as a significant or distinguished advisor to another entity.
-
C.
worksAsConsultantFor
Indicates that one entity provides professional consulting services to another entity, typically on a contractual or advisory basis.
-
D.
isPrincipalAdvisorTo
Indicates that one entity serves as the main or primary advisor to another entity, providing overarching guidance or counsel.
-
E.
typeOfAdviser
Indicates the specific advisory role or category that an adviser holds in relation to 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_69f224a3307081909a6dca8ca75dbf48 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fe96c2647c819082989f11e1ae3d35 |
completed | May 9, 2026, 2:06 a.m. |
| PD | Predicate disambiguation | batch_69fe928615448190af939e5a94be55bb |
completed | May 9, 2026, 1:48 a.m. |
Created at: April 29, 2026, 8:26 p.m.