Triple
T25284508
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | American Depositary Share |
E633900
|
entity |
| Predicate | isSettledIn |
P158339
|
FINISHED |
| Object | U.S. dollar |
—
|
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: U.S. dollar | Statement: [American Depositary Share, isSettledIn, U.S. dollar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSettledIn Context triple: [American Depositary Share, isSettledIn, U.S. dollar]
-
A.
laterSettledIn
Indicates that one entity moved to and established residence in a place or community at a subsequent time, after an earlier location or phase in their life.
-
B.
settled
Indicates that an entity established residence or a stable presence in a place, typically after moving from elsewhere.
-
C.
settledAs
Indicates that one entity has been resolved, finalized, or agreed upon in the form or status of another entity.
-
D.
settledInYear
Indicates the specific calendar year in which an entity became established, inhabited, or formally settled in a particular place or status.
-
E.
resettledAt
Indicates that an entity has moved and established residence or presence at a new location.
- 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_69e75a9402fc81909362ca85277c06d9 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f48e0800a881909bf6099d120338a5 |
completed | May 1, 2026, 11:27 a.m. |
| PD | Predicate disambiguation | batch_69f45d06d0388190b36ecde92013624a |
completed | May 1, 2026, 7:57 a.m. |
| PDg | Predicate description generation | batch_69f465699c9c8190ac7b4b32b782550c |
completed | May 1, 2026, 8:33 a.m. |
Created at: April 21, 2026, 1:19 p.m.