Triple
T24274508
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | XEL |
E605369
|
entity |
| Predicate | issuerProvidesServiceIn |
P35398
|
FINISHED |
| Object | United States |
—
|
NE NERFINISHED |
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: United States | Statement: [XEL, issuerProvidesServiceIn, United States]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: issuerProvidesServiceIn Context triple: [XEL, issuerProvidesServiceIn, United States]
-
A.
issuerType
Indicates the classification or category of the entity that issues something (such as a document, credential, or instrument).
-
B.
issuerProduces
Indicates that an issuer creates, generates, or brings into existence a particular product, document, asset, or item.
-
C.
issuerOperatesIn
chosen
Indicates that an issuing entity conducts business activities or has operational presence within a specified geographic area or jurisdiction.
-
D.
mayProvideServiceIn
Indicates that one entity is permitted or authorized to offer or perform a service within the scope, area, or context defined by another entity.
-
E.
issuerMainPlatform
Indicates that an entity serves as the primary platform or main environment through which an issuer operates, offers, or manages its services or instruments.
- 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_69e2954707dc8190915551eb114cfff6 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f28d5da53c8190810f4e7777d112ba |
completed | April 29, 2026, 10:59 p.m. |
| PD | Predicate disambiguation | batch_69f1c457a2908190993824395b3c365d |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 18, 2026, 12:07 a.m.