Triple
T30984188
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LSE: HOF |
E789473
|
entity |
| Predicate | hadIssuerLegalForm |
P51147
|
FINISHED |
| Object | public limited company |
—
|
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: public limited company | Statement: [LSE: HOF, hadIssuerLegalForm, public limited company]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadIssuerLegalForm Context triple: [LSE: HOF, hadIssuerLegalForm, public limited company]
-
A.
issuerFormationMethod
Indicates the method or process by which an issuer was created or legally formed.
-
B.
hasUnderlyingCompanyLegalForm
Indicates that an entity is associated with, or governed by, a specific underlying legal form of a company.
-
C.
hasIssuerPrimaryBusiness
Indicates that an entity’s main or primary line of business is identified or characterized by the associated business activity or classification.
-
D.
issuerFounded
Indicates that one entity is the organization or person that established or created the other entity at its founding.
-
E.
belongsToCompanyLegalForm
chosen
Indicates that an entity is associated with or classified under a specific legal form of a company.
- 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_69f224c550b081909ddfceb0c3d03bdd |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6953bafb88190a860e9c68a3dd4b2 |
completed | May 3, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69f690ef92308190903a54fc74233269 |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 29, 2026, 8:55 p.m.