Triple
T26066709
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1st Baron Passfield |
E657421
|
entity |
| Predicate | titleHolderCoFounderOf |
P175199
|
FINISHED |
| Object | London School of Economics |
—
|
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: London School of Economics | Statement: [1st Baron Passfield, titleHolderCoFounderOf, London School of Economics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleHolderCoFounderOf Context triple: [1st Baron Passfield, titleHolderCoFounderOf, London School of Economics]
-
A.
cofounderOf
Indicates that a person jointly established or created an organization, company, or project with one or more other founders.
-
B.
coFounderOfFounder
Indicates that one entity is a co-founder of another entity who is themselves a founder of something else.
-
C.
titleHolderFullName
Indicates the full personal name of the entity that holds a particular title or position.
-
D.
titleHolderName
Indicates the name of the person or entity that holds a particular title or position.
-
E.
titleHolderServedAs
Indicates that the entity holding a particular title also performed the role or function associated with that title.
- F. None of above. chosen
Provenance (4 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_69ee5bbe539081909efc7f9dd7c1b53c |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f6cee547108190ad3bc84297d8f516 |
completed | May 3, 2026, 4:28 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1188708190b8f0f56e595e6057 |
completed | May 3, 2026, 4:16 a.m. |
| PDg | Predicate description generation | batch_69f6cee3604c81908a07eade2f39064e |
completed | May 3, 2026, 4:28 a.m. |
Created at: April 26, 2026, 7:24 p.m.