Triple
T17338595
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Calvert Formation |
E421005
|
entity |
| Predicate | collectingSiteType |
P53032
|
FINISHED |
| Object | fossil collecting area |
—
|
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: fossil collecting area | Statement: [Calvert Formation, collectingSiteType, fossil collecting area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: collectingSiteType Context triple: [Calvert Formation, collectingSiteType, fossil collecting area]
-
A.
associatedSiteType
chosen
Indicates the type or category of site with which an entity is associated.
-
B.
hasCapitalSiteType
Indicates the type or classification of the site that serves as the capital for an entity.
-
C.
operatesOnSiteType
Indicates that an entity conducts its operations or activities at, or in association with, a specified type of site or location.
-
D.
isSiteOf
Indicates that a location or place serves as the setting or host for a particular event, activity, or feature.
-
E.
collectingArea
Indicates the total surface area over which something (typically a device or system) gathers or receives a substance, signal, or resource.
- 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_69d889d3adc881909319f1edb8d2a956 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43a13dd44819091d296c764976dfe |
completed | April 19, 2026, 2:12 a.m. |
| PD | Predicate disambiguation | batch_69e3b021a5bc81909ae55406f9d0b37f |
completed | April 18, 2026, 4:24 p.m. |
Created at: April 10, 2026, 5:43 a.m.