Triple
T1633485
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pacific Shores |
E35309
|
entity |
| Predicate | featuresHabitatType |
P22357
|
FINISHED |
| Object | rocky shore habitat |
—
|
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: rocky shore habitat | Statement: [Pacific Shores, featuresHabitatType, rocky shore habitat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresHabitatType Context triple: [Pacific Shores, featuresHabitatType, rocky shore habitat]
-
A.
featuresHabitat
chosen
Indicates that something includes or provides a particular habitat as part of its characteristics or environment.
-
B.
hasBiodiversityFeature
Indicates that an entity possesses or is associated with a specific biodiversity-related characteristic, attribute, or element.
-
C.
featuresSpecies
Indicates that something includes, presents, or highlights a particular species as part of its content or composition.
-
D.
vegetationType
Indicates the specific kind or category of plant cover or flora that characterizes a given area or environment.
-
E.
faunaCharacteristic
Indicates that an entity has a specific trait, feature, or quality related to animals or animal life.
- 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_69a886036bc081909ff5de16dbe5e8ea |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a96083e7308190abbf025fe8e43abb |
completed | March 5, 2026, 10:52 a.m. |
| PD | Predicate disambiguation | batch_69a907cac610819083cafd4396b6d66c |
completed | March 5, 2026, 4:34 a.m. |
Created at: March 4, 2026, 7:28 p.m.