Triple
T6297715
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mole Cave |
E141171
|
entity |
| Predicate | hasTypeOfDeposits |
P68168
|
FINISHED |
| Object | fossiliferous breccia |
—
|
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: fossiliferous breccia | Statement: [Mole Cave, hasTypeOfDeposits, fossiliferous breccia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeOfDeposits Context triple: [Mole Cave, hasTypeOfDeposits, fossiliferous breccia]
-
A.
typeOfDeposits
chosen
Indicates the specific kinds or categories of deposits associated with an account, entity, or transaction.
-
B.
hasDeposits
Indicates that an entity holds or maintains deposited funds or resources in another entity, such as an account or institution.
-
C.
hasMajorDepositIn
Indicates that an entity possesses a significant or primary deposit, typically of a resource or asset, located in a specified place.
-
D.
typeOfDepositInsurance
Indicates the specific kind or category of deposit insurance that applies to a financial account or institution.
-
E.
hasBankType
Indicates that an entity is associated with or classified by a particular type or category of bank.
- 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_69c008cdf2ac8190bb640c94478fb4ed |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0643bd0748190af7abbebb6f94242 |
completed | March 22, 2026, 9:50 p.m. |
| PD | Predicate disambiguation | batch_69c060df0d8881908215575862ef6831 |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:27 p.m.