Triple
T38098487
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Forbes' Quarry Cave |
E951310
|
entity |
| Predicate | skullFoundIn |
P173618
|
FINISHED |
| Object | 1848 |
—
|
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: 1848 | Statement: [Forbes' Quarry Cave, skullFoundIn, 1848]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: skullFoundIn Context triple: [Forbes' Quarry Cave, skullFoundIn, 1848]
-
A.
fossilsFoundAt
chosen
Indicates that fossil remains of an organism or taxon have been discovered at a particular location or site.
-
B.
fossilsFoundOn
Indicates that fossils are discovered or located on a particular surface, layer, or object.
-
C.
estimatedNumberOfSkulls
Indicates the approximate count of skulls associated with an entity, based on estimation rather than an exact measurement.
-
D.
skullUsage
Indicates how a skull is used, applied, or functionally involved in a particular context or activity.
-
E.
discoveredRemainsIn
Indicates that one entity found or uncovered the physical remains of another entity at a specific location.
- 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_69f76f04960c8190a83f14ae4c67f5bc |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fc4748843c8190931432653be4890c |
completed | May 7, 2026, 8:03 a.m. |
| PD | Predicate disambiguation | batch_69fc45646ce481908caf292ff9f06e15 |
completed | May 7, 2026, 7:55 a.m. |
Created at: May 3, 2026, 4:21 p.m.