Triple
T14304999
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Botucatu |
E354670
|
entity |
| Predicate | hasNearbyBiome |
P41431
|
FINISHED |
| Object | Atlantic Forest remnants |
—
|
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: Atlantic Forest remnants | Statement: [Botucatu, hasNearbyBiome, Atlantic Forest remnants]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyBiome Context triple: [Botucatu, hasNearbyBiome, Atlantic Forest remnants]
-
A.
isLocatedInBiome
Indicates that one entity is situated within or belongs to the environmental region or biome represented by another entity.
-
B.
hasNearbyHabitats
Indicates that one entity has other habitats located close to it in geographic or spatial terms.
-
C.
hasNearbyLandscapeType
Indicates that one entity is located close to, or in the vicinity of, a particular type of landscape.
-
D.
hasSecondaryBiome
Indicates that an entity is associated with an additional, subordinate biome type beyond its primary biome.
-
E.
hasNearbyForestType
chosen
Indicates that one entity is located close to, or in the vicinity of, a forest of a specified type.
- 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_69d8278ed42c8190b9f882dcce611347 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de85afabe48190926d6098047f4bcf |
completed | April 14, 2026, 6:21 p.m. |
| PD | Predicate disambiguation | batch_69de2a8f81f08190af737e1654847aa6 |
completed | April 14, 2026, 11:52 a.m. |
Created at: April 10, 2026, 1:12 a.m.