Triple
T33004023
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Worshipful Company of Tax Advisers |
E844444
|
entity |
| Predicate | foundedAsGuild |
P196753
|
FINISHED |
| Object | 1995 |
—
|
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: 1995 | Statement: [Worshipful Company of Tax Advisers, foundedAsGuild, 1995]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundedAsGuild Context triple: [Worshipful Company of Tax Advisers, foundedAsGuild, 1995]
-
A.
foundedAs
Indicates the original name or form under which an organization, institution, or entity was first established.
-
B.
factionFounded
Indicates that an organization or group was established or created by a particular faction.
-
C.
foundingClub
Indicates that one entity is a club that participated as a founding member in the creation or establishment of another entity (such as a league, organization, or competition).
-
D.
foundedFor
Indicates that an entity was established or created specifically to serve, support, or benefit another entity or purpose.
-
E.
foundedWith
Indicates that an entity was established or created together with another entity, typically as co-founders or jointly initiated partners.
- 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_69f3494e59f08190b9127c693e5c7e8f |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fe6739d4dc8190ae7505c089bbac29 |
completed | May 8, 2026, 10:44 p.m. |
| PD | Predicate disambiguation | batch_69fe6541dffc81909c66a61ba69f38fc |
completed | May 8, 2026, 10:35 p.m. |
| PDg | Predicate description generation | batch_69fe673905408190a2ae68c2c9563403 |
completed | May 8, 2026, 10:44 p.m. |
Created at: May 1, 2026, 1:23 a.m.