Triple
T12524385
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ERIC-B |
E299397
|
entity |
| Predicate | hasIssuerLegalForm |
P96805
|
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: [ERIC-B, hasIssuerLegalForm, public limited company]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIssuerLegalForm Context triple: [ERIC-B, hasIssuerLegalForm, public limited company]
-
A.
hasIssuerPrimaryBusiness
Indicates that an entity’s main or primary line of business is identified or characterized by the associated business activity or classification.
-
B.
hasUnderlyingCompanyLegalForm
Indicates that an entity is associated with, or governed by, a specific underlying legal form of a company.
-
C.
belongsToCompanyLegalForm
Indicates that an entity is associated with or classified under a specific legal form of a company.
-
D.
typicalIssuer
Indicates that one entity is the standard or commonly expected issuer (e.g., of a document, instrument, or credential) for another entity.
-
E.
hasLegalStructure
chosen
Indicates that an entity possesses a specific formal legal organization or classification under law.
- 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_69d6ada5cdd48190860d9ce30aff69be |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d95f5507b481908d13cc317b7402f6 |
completed | April 10, 2026, 8:36 p.m. |
| PD | Predicate disambiguation | batch_69d9540d7b788190a0d57b098e90e491 |
completed | April 10, 2026, 7:48 p.m. |
Created at: April 8, 2026, 9:57 p.m.