Triple
T21248964
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British–Irish Ice Sheet |
E523689
|
entity |
| Predicate | leftDeposits |
P143373
|
FINISHED |
| Object | till |
—
|
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: till | Statement: [British–Irish Ice Sheet, leftDeposits, till]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leftDeposits Context triple: [British–Irish Ice Sheet, leftDeposits, till]
-
A.
commonDeposits
Indicates that two or more entities share the same or overlapping deposit locations or accounts.
-
B.
hasDeposits
Indicates that an entity holds or maintains deposited funds or resources in another entity, such as an account or institution.
-
C.
deposited
Indicates that an entity has placed or put something into another entity, typically transferring it into a container, location, or account.
-
D.
typicalDeposits
Indicates that the associated value represents the usual or standard amount of deposits expected for an entity or account.
-
E.
depositary
Indicates that one entity holds or safeguards something (such as assets, documents, or funds) on behalf of another entity.
- 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_69e0b5146c108190adc9adb73e90abff |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7359c7a648190b4345336ac3be024 |
completed | April 21, 2026, 8:30 a.m. |
| PD | Predicate disambiguation | batch_69e5f61239708190ab7b3c83ae848a0d |
completed | April 20, 2026, 9:46 a.m. |
| PDg | Predicate description generation | batch_69e5f9943ed881909ef49045c5bcf6df |
completed | April 20, 2026, 10:01 a.m. |
Created at: April 16, 2026, 3:56 p.m.