Triple
T19305574
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crocodylus raninus |
E482817
|
entity |
| Predicate | livesInBiome |
P110631
|
FINISHED |
| Object | tropical rainforest |
—
|
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: tropical rainforest | Statement: [Crocodylus raninus, livesInBiome, tropical rainforest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: livesInBiome Context triple: [Crocodylus raninus, livesInBiome, tropical rainforest]
-
A.
isLocatedInBiome
chosen
Indicates that one entity is situated within or belongs to the environmental region or biome represented by another entity.
-
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.
biome
Indicates the type of ecological environment or habitat in which an entity naturally exists or is situated.
-
D.
hasSecondaryBiome
Indicates that an entity is associated with an additional, subordinate biome type beyond its primary biome.
-
E.
hasTerrestrialHabitat
Indicates that an entity lives primarily on land or in a ground-based environment rather than in aquatic or aerial habitats.
- 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_69d8e8d04d5c8190baa816986f2b1d1e |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e604c84fe08190869463bdd0324160 |
completed | April 20, 2026, 10:49 a.m. |
| PD | Predicate disambiguation | batch_69e4dd0bc7508190a6f9d56bd4c3404f |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:31 p.m.