Triple
T19288125
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SPDR |
E482366
|
entity |
| Predicate | hasRegionExposure |
P23750
|
FINISHED |
| Object | United States equities |
—
|
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: United States equities | Statement: [SPDR, hasRegionExposure, United States equities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRegionExposure Context triple: [SPDR, hasRegionExposure, United States equities]
-
A.
hasRegion
Indicates that an entity includes, contains, or is associated with a specific geographic or administrative region as part of its scope or structure.
-
B.
regionExposure
chosen
Indicates that an entity is subject to or affected by exposure within a specific geographic or spatial region.
-
C.
hasRegionStrongPresence
Indicates that an entity maintains a significant, influential, or concentrated presence within a specified region.
-
D.
hasNotableRegionOfExport
Indicates that an entity is associated with a specific geographic region from which it is prominently or significantly exported.
-
E.
hasBroadRegion
Indicates that an entity is associated with, located in, or applicable to a relatively large or general geographic or conceptual region.
- 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_69d8e8cf61b0819096fe3e4107827c4e |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fc043fa481909bbe281a70fb508e |
completed | April 20, 2026, 10:12 a.m. |
| PD | Predicate disambiguation | batch_69e4dd0bc7508190a6f9d56bd4c3404f |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:30 p.m.