Triple
T28554112
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jewish Colonial Trust |
E722959
|
entity |
| Predicate | sharesSoldIn |
P83121
|
FINISHED |
| Object | Europe |
—
|
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: Europe | Statement: [Jewish Colonial Trust, sharesSoldIn, Europe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesSoldIn Context triple: [Jewish Colonial Trust, sharesSoldIn, Europe]
-
A.
sharesTradedFor
Indicates that shares of one entity are exchanged or traded in return for another asset, security, or form of consideration.
-
B.
soldStakeIn
Indicates that one entity has transferred ownership of a share or interest it held in another entity or asset to a different party.
-
C.
someAssetsSoldTo
Indicates that a subset of an entity’s assets has been transferred in ownership to another party through a sale.
-
D.
soldDuring
Indicates that a selling transaction or event occurred within the time span of a specified period or event.
-
E.
soldWellIn
chosen
Indicates that something achieved strong sales performance within a particular market, region, or time period.
- 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_69f01a60204481909af1bb76247b8221 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69fd57ba740c8190bd1d40166fccccb7 |
completed | May 8, 2026, 3:25 a.m. |
| PD | Predicate disambiguation | batch_69fd55ee82b881908a639da3a41b3af6 |
completed | May 8, 2026, 3:18 a.m. |
Created at: April 28, 2026, 3:44 a.m.