Triple
T31994087
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Birket Qarun |
E816946
|
entity |
| Predicate | hasFossilLocalities |
P14600
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Birket Qarun, hasFossilLocalities, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFossilLocalities Context triple: [Birket Qarun, hasFossilLocalities, true]
-
A.
fossilsFoundAt
Indicates that fossil remains of an organism or taxon have been discovered at a particular location or site.
-
B.
fossilTypeLocality
Indicates the specific locality that serves as the reference site where the defining fossil specimen(s) of a particular fossil type were originally found.
-
C.
hasNotableFossilSite
chosen
Indicates that an entity contains or is associated with a fossil site recognized as significant or noteworthy.
-
D.
containsFossilsOf
Indicates that one entity (typically a geological formation, rock, or sample) includes fossil remains or traces belonging to another entity (an organism or taxon).
-
E.
discoveredAsFossilSite
Indicates that a location was identified and recognized as a site containing fossils.
- 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_69f348f8002081909a3588758ba94afb |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fd4d1854988190be093b103a681798 |
completed | May 8, 2026, 2:40 a.m. |
| PD | Predicate disambiguation | batch_69fd4c8d1a188190897c24527337814a |
completed | May 8, 2026, 2:38 a.m. |
Created at: May 1, 2026, 12:13 a.m.