Triple
T13407967
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | largemouth bass |
E320010
|
entity |
| Predicate | preferredHabitatFeature |
P96824
|
FINISHED |
| Object | vegetated areas |
—
|
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: vegetated areas | Statement: [largemouth bass, preferredHabitatFeature, vegetated areas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: preferredHabitatFeature Context triple: [largemouth bass, preferredHabitatFeature, vegetated areas]
-
A.
preferredHabitat
Indicates the type of environment or habitat in which an entity most commonly lives or thrives.
-
B.
featuresHabitat
Indicates that something includes or provides a particular habitat as part of its characteristics or environment.
-
C.
usesHabitatFeature
chosen
Indicates that an organism makes use of a particular habitat feature (such as a structure, resource, or microhabitat) as part of its behavior or life history.
-
D.
preferredClimate
Indicates the type of climate that an entity favors or is most suited to.
-
E.
hasBiodiversityFeature
Indicates that an entity possesses or is associated with a specific biodiversity-related characteristic, attribute, or element.
- 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_69d806b943cc8190b6af624d385d7e12 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbae4d2c5481908facfaaa1501e344 |
completed | April 12, 2026, 2:38 p.m. |
| PD | Predicate disambiguation | batch_69d9a0355de48190bb3fb96912e20df3 |
completed | April 11, 2026, 1:13 a.m. |
Created at: April 9, 2026, 9:35 p.m.