Triple
T20272686
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DE0008404005 |
E502928
|
entity |
| Predicate | relatedLEIIssuer |
P139504
|
FINISHED |
| Object | 529900MUF4C0OZP8XN24 |
—
|
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: 529900MUF4C0OZP8XN24 | Statement: [DE0008404005, relatedLEIIssuer, 529900MUF4C0OZP8XN24]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedLEIIssuer Context triple: [DE0008404005, relatedLEIIssuer, 529900MUF4C0OZP8XN24]
-
A.
externalRelations
Indicates that an entity has relationships, interactions, or connections with entities outside its own immediate group, system, or organization.
-
B.
issuerAlsoKnownFor
Indicates that the issuer is additionally recognized or notable for another role, activity, or attribute beyond their primary identified capacity.
-
C.
relatedCompanyType
Indicates the type or nature of the relationship that one company has to another company.
-
D.
relatedExchange
Indicates that there is a connection or association between two exchanges or exchange-related events.
-
E.
relatedPass
Indicates that one pass is associated with or connected to another pass in some relevant way.
- 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_69e0b4b0e79c8190bd61f22ef1329fa8 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e675dff3c4819098ba45eba4e7b296 |
completed | April 20, 2026, 6:52 p.m. |
| PD | Predicate disambiguation | batch_69e55b1e5e1c8190ba8a5544b1db9e1d |
completed | April 19, 2026, 10:45 p.m. |
| PDg | Predicate description generation | batch_69e56702ad04819099c1c08f28d16809 |
completed | April 19, 2026, 11:36 p.m. |
Created at: April 16, 2026, 10:15 a.m.