Triple
T6099507
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WWF ecoregion classification |
E135958
|
entity |
| Predicate | numberOfBiogeographicRealms |
P2355
|
FINISHED |
| Object | 8 |
—
|
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: 8 | Statement: [WWF ecoregion classification, numberOfBiogeographicRealms, 8]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfBiogeographicRealms Context triple: [WWF ecoregion classification, numberOfBiogeographicRealms, 8]
-
A.
belongsToBiogeographicRealm
Indicates that an entity (such as a species, habitat, or location) is associated with or falls within a particular biogeographic realm.
-
B.
numberOfSpecies
Indicates the count of distinct species associated with a given entity or context.
-
C.
ecoregionsInclude
Indicates that one ecoregion spatially contains or encompasses another ecoregion or area within its boundaries.
-
D.
numberOfRegions
chosen
Indicates the total count of distinct regions associated with or contained within a given entity.
-
E.
biogeographicClassificationSystem
Indicates the system or scheme used to classify and organize entities according to their biogeographic regions or distributions.
- 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_69c0087cd3c48190b459848c72d84eb1 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c05b3970808190ba90f5e4235db9f2 |
completed | March 22, 2026, 9:12 p.m. |
| PD | Predicate disambiguation | batch_69c049f5ac988190b62ba565153aaa35 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:13 p.m.