Triple
T20246947
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bryoria lichens |
E498446
|
entity |
| Predicate | microhabitatFor |
P25732
|
FINISHED |
| Object | arthropods |
—
|
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: arthropods | Statement: [Bryoria lichens, microhabitatFor, arthropods]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: microhabitatFor Context triple: [Bryoria lichens, microhabitatFor, arthropods]
-
A.
microhabitat
chosen
Indicates a specific, localized habitat or environmental niche within a larger habitat where an organism lives or an interaction occurs.
-
B.
preferredHabitat
Indicates the type of environment or habitat in which an entity most commonly lives or thrives.
-
C.
featuresHabitat
Indicates that something includes or provides a particular habitat as part of its characteristics or environment.
-
D.
typicalHabitatInHost
Indicates that an organism’s usual or characteristic habitat occurs within a particular host organism.
-
E.
simulatesHabitatOf
Indicates that one entity artificially recreates or models the living conditions or environment characteristic of another entity’s natural habitat.
- 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_69da6274c58c81909c646eabed6f4f30 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e673a3c61481909413e042d76cc580 |
completed | April 20, 2026, 6:42 p.m. |
| PD | Predicate disambiguation | batch_69e55b1b23f88190bdcbe2f81dd226dd |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 11, 2026, 11:40 p.m.