Triple
T18897810
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cerrado |
E462253
|
entity |
| Predicate | hasReptileSpeciesCount |
P6211
|
FINISHED |
| Object | over 180 reptile species |
—
|
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: over 180 reptile species | Statement: [Cerrado, hasReptileSpeciesCount, over 180 reptile species]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReptileSpeciesCount Context triple: [Cerrado, hasReptileSpeciesCount, over 180 reptile species]
-
A.
hasReptileSpecies
Indicates that one entity possesses, contains, or is associated with a reptile species as part of its characteristics or composition.
-
B.
numberOfSpecies
chosen
Indicates the count of distinct species associated with a given entity or context.
-
C.
speciesNumber
Indicates the numerical identifier or count associated with a particular species in a given context.
-
D.
hasEndemicSpecies
Indicates that a place or region contains species that are native to and found only within that specific geographic area.
-
E.
containsVenomousSpecies
Indicates that the referenced entity includes within it one or more species that are venomous.
- 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_69d8dcfd05bc819088903cca13cc2846 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c52689308190b2e5ca163b1f6cd1 |
completed | April 20, 2026, 6:18 a.m. |
| PD | Predicate disambiguation | batch_69e4a2e27e1481908a8da10b28f07875 |
completed | April 19, 2026, 9:39 a.m. |
Created at: April 10, 2026, 11:58 a.m.