Triple
T30502275
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Exchange Traded Commodity |
E776166
|
entity |
| Predicate | isOftenDomiciledIn |
P118897
|
FINISHED |
| Object | European jurisdictions |
—
|
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: European jurisdictions | Statement: [Exchange Traded Commodity, isOftenDomiciledIn, European jurisdictions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOftenDomiciledIn Context triple: [Exchange Traded Commodity, isOftenDomiciledIn, European jurisdictions]
-
A.
hasBranchResidenceIn
Indicates that an organization maintains a branch or subsidiary located in a specified place or jurisdiction.
-
B.
hasResidenceIn
Indicates that an entity lives or maintains a primary dwelling in a specified location.
-
C.
hasNumberOfResidences
Indicates the quantity of separate residences associated with a given entity.
-
D.
likelyResidence
chosen
Indicates that an entity is probably located at, lives at, or is most commonly associated with a particular place of residence.
-
E.
isPermanentHomeOf
Indicates that a location serves as the long-term, primary residence for a particular entity.
- 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_69f22498c5d481908aaea89e6fab8280 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f687812a6481908b126c0aacd38936 |
completed | May 2, 2026, 11:23 p.m. |
| PD | Predicate disambiguation | batch_69f67e42d6688190b60e91d2c388c555 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 29, 2026, 8:15 p.m.