Triple
T1082978
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Invesco QQQ Trust |
E23987
|
entity |
| Predicate | regionExposure |
P23750
|
FINISHED |
| Object | primarily United States |
—
|
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: primarily United States | Statement: [Invesco QQQ Trust, regionExposure, primarily United States]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionExposure Context triple: [Invesco QQQ Trust, regionExposure, primarily United States]
-
A.
regionException
Indicates an exception or exclusion to a rule, condition, or classification that applies specifically to a certain region or set of regions.
-
B.
regionCoverage
Indicates that one entity geographically spans, includes, or serves the area defined by another entity.
-
C.
regionRuled
Indicates that a particular region is governed or controlled by a specified ruler or authority.
-
D.
regionSpecialization
Indicates that a region is designated or recognized as being particularly focused on, adapted to, or specialized in a specific function, activity, or domain.
-
E.
observedInRegion
Indicates that something has been detected, recorded, or seen occurring within a specified geographic or spatial region.
- 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_69a493f1ddf48190a99d54b00e99f8ce |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b95e56948190a1e92367ad7240b7 |
completed | March 1, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69a4b73f4310819086281f8ec67d1a32 |
completed | March 1, 2026, 10:01 p.m. |
| PDg | Predicate description generation | batch_69a4b80f0fb08190a19a50e38ae8f16c |
completed | March 1, 2026, 10:05 p.m. |
Created at: March 1, 2026, 7:42 p.m.