Triple
T28817269
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anisian |
E727671
|
entity |
| Predicate | containsBiozones |
P69704
|
FINISHED |
| Object | ammonoid biozones |
—
|
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: ammonoid biozones | Statement: [Anisian, containsBiozones, ammonoid biozones]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsBiozones Context triple: [Anisian, containsBiozones, ammonoid biozones]
-
A.
biogeographicZone
Indicates the biogeographic region or ecological zone in which an entity (such as a species or habitat) naturally occurs or is distributed.
-
B.
biomeIncludes
Indicates that a biome contains or encompasses a particular entity, such as a species, habitat, or environmental feature, as part of its composition.
-
C.
hasEcologicalZones
chosen
Indicates that an entity is associated with, contains, or is characterized by one or more distinct ecological zones.
-
D.
hasBiosphere
Indicates that an entity possesses or supports a biosphere, i.e., a region where living organisms and ecological processes exist.
-
E.
hasBiodiversityFeature
Indicates that an entity possesses or is associated with a specific biodiversity-related characteristic, attribute, or element.
- 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_69f0319d09088190bbf14cdf1987792a |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69fdd2be648c8190b60b3d1caeb44364 |
completed | May 8, 2026, 12:10 p.m. |
| PD | Predicate disambiguation | batch_69fdd14a5c708190a6f95ec61f4fc28f |
completed | May 8, 2026, 12:04 p.m. |
Created at: April 28, 2026, 6:33 a.m.