Triple
T24056806
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paranthropus boisei |
E595828
|
entity |
| Predicate | fossilRangeRegion |
P117889
|
FINISHED |
| Object | Eastern Africa |
—
|
NE NERFINISHED |
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: Eastern Africa | Statement: [Paranthropus boisei, fossilRangeRegion, Eastern Africa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fossilRangeRegion Context triple: [Paranthropus boisei, fossilRangeRegion, Eastern Africa]
-
A.
fossilRangeQualifier
Indicates how the temporal range of a fossil (e.g., its first or last appearance in the geologic record) should be interpreted, refined, or qualified.
-
B.
fossilDistribution
chosen
Indicates the geographic or stratigraphic locations where fossils of an organism or taxon have been found.
-
C.
geologicalRange
Indicates the span of geological time during which an entity (such as a taxon or formation) is known to have existed or been present.
-
D.
zoogeographicRegion
Indicates the zoogeographic region in which an organism or taxon naturally occurs or is distributed.
-
E.
paleogeographicAffinity
Indicates a relationship where entities share or are associated with a particular ancient geographic region or configuration of the Earth's surface.
- 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_69e288c184b081909f1f1751fb8e299a |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1da50d6108190a36bffaa475c8b93 |
completed | April 29, 2026, 10:15 a.m. |
| PD | Predicate disambiguation | batch_69f1764b1d4c8190b12590c6339c31c1 |
completed | April 29, 2026, 3:08 a.m. |
Created at: April 17, 2026, 10:34 p.m.