Triple
T10634058
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Plover’s Lake |
E250531
|
entity |
| Predicate | hasStratifiedDeposits |
P95088
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Plover’s Lake, hasStratifiedDeposits, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStratifiedDeposits Context triple: [Plover’s Lake, hasStratifiedDeposits, yes]
-
A.
hasDeposits
Indicates that an entity holds or maintains deposited funds or resources in another entity, such as an account or institution.
-
B.
hasMajorDepositIn
Indicates that an entity possesses a significant or primary deposit, typically of a resource or asset, located in a specified place.
-
C.
typeOfDeposits
Indicates the specific kinds or categories of deposits associated with an account, entity, or transaction.
-
D.
hasStratificationType
Indicates the specific manner or pattern in which something is stratified or layered.
-
E.
commonDeposits
Indicates that two or more entities share the same or overlapping deposit locations or accounts.
- 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_69d6aa5993448190a493b790b8f85010 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6dfab47bc819086684edc1b6dce74 |
completed | April 8, 2026, 11:07 p.m. |
| PD | Predicate disambiguation | batch_69d6dd83b114819098e84dc658e82d7e |
completed | April 8, 2026, 10:58 p.m. |
| PDg | Predicate description generation | batch_69d6df463ea8819091d6683e476b4f21 |
completed | April 8, 2026, 11:05 p.m. |
Created at: April 8, 2026, 9:02 p.m.