Triple
T18897812
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cerrado |
E462253
|
entity |
| Predicate | hasFishSpeciesCount |
P6211
|
FINISHED |
| Object | over 1,200 fish 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 1,200 fish species | Statement: [Cerrado, hasFishSpeciesCount, over 1,200 fish species]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFishSpeciesCount Context triple: [Cerrado, hasFishSpeciesCount, over 1,200 fish species]
-
A.
hasFishingSpecies
Indicates that a location, body of water, or fishing area supports or contains one or more specific species that can be fished there.
-
B.
hasFishCountingFacility
Indicates that a location or structure is equipped with a facility specifically designed for counting fish.
-
C.
hasPrimaryFishSpecies
Indicates that an entity is characterized by or associated with a particular main or dominant fish species.
-
D.
numberOfSpecies
chosen
Indicates the count of distinct species associated with a given entity or context.
-
E.
hasMarineSpecies
Indicates that an entity contains, supports, or is associated with one or more marine species.
- 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.