Triple
T15231272
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LLOY |
E364006
|
entity |
| Predicate | issuerLEI |
P117661
|
FINISHED |
| Object | 549300PPXHEU2JF0AM85 |
—
|
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: 549300PPXHEU2JF0AM85 | Statement: [LLOY, issuerLEI, 549300PPXHEU2JF0AM85]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: issuerLEI Context triple: [LLOY, issuerLEI, 549300PPXHEU2JF0AM85]
-
A.
issuerOperatesIn
Indicates that an issuing entity conducts business activities or has operational presence within a specified geographic area or jurisdiction.
-
B.
issuerType
Indicates the classification or category of the entity that issues something (such as a document, credential, or instrument).
-
C.
issuerCEO
Indicates that the subject entity serves as the chief executive officer (CEO) of the issuer entity.
-
D.
issuerFounded
Indicates that one entity is the organization or person that established or created the other entity at its founding.
-
E.
issuerAlsoKnownFor
Indicates that the issuer is additionally recognized or notable for another role, activity, or attribute beyond their primary identified capacity.
- 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_69d85a0ce24c81909c4d3b6475548c95 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0078e27408190bc13c0ca441f5594 |
completed | April 15, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69deca899d5c8190be4a7c71e1683c69 |
completed | April 14, 2026, 11:15 p.m. |
| PDg | Predicate description generation | batch_69decf2ca6148190967c319728ec3661 |
completed | April 14, 2026, 11:35 p.m. |
Created at: April 10, 2026, 3:12 a.m.