Triple
T16303304
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kounotori |
E395842
|
entity |
| Predicate | typicalHabitatOfReferent |
P76824
|
FINISHED |
| Object | wetlands |
—
|
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: wetlands | Statement: [Kounotori, typicalHabitatOfReferent, wetlands]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalHabitatOfReferent Context triple: [Kounotori, typicalHabitatOfReferent, wetlands]
-
A.
featuresHabitat
Indicates that something includes or provides a particular habitat as part of its characteristics or environment.
-
B.
preferredHabitat
chosen
Indicates the type of environment or habitat in which an entity most commonly lives or thrives.
-
C.
simulatesHabitatOf
Indicates that one entity artificially recreates or models the living conditions or environment characteristic of another entity’s natural habitat.
-
D.
onlyNaturalHabitatOf
Indicates that a given location is the sole natural habitat where a particular species or organism occurs in the wild.
-
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_69d87f23bb088190a16fbb91a1957ea5 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e25e35157481909e5604b7dae7a2a2 |
completed | April 17, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69e219fa5508819097e9d383348bf174 |
completed | April 17, 2026, 11:31 a.m. |
Created at: April 10, 2026, 5:06 a.m.