Triple
T22948993
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Common kingfisher |
E569953
|
entity |
| Predicate | perchingPreference |
P75263
|
FINISHED |
| Object | low branches or posts over water |
—
|
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: low branches or posts over water | Statement: [Common kingfisher, perchingPreference, low branches or posts over water]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: perchingPreference Context triple: [Common kingfisher, perchingPreference, low branches or posts over water]
-
A.
perchingSite
chosen
Indicates a location or object where an entity (typically an animal, such as a bird) rests or sits temporarily.
-
B.
birdHabitatType
Indicates the type of natural environment or habitat in which a bird typically lives or is commonly found.
-
C.
hasPerchDepicted
Indicates that a perch (such as a resting place or support for an animal or object) is visually represented or shown in association with the subject.
-
D.
roostType
Indicates the type or kind of roost (e.g., structure or location) an animal uses for resting or nesting.
-
E.
birdPosition
Indicates the spatial location or placement of a bird relative to a reference frame or environment.
- 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_69e2459199d08190a8184ee2aa935842 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f181a085188190b06ffa227087302d |
completed | April 29, 2026, 3:57 a.m. |
| PD | Predicate disambiguation | batch_69ef3b882e708190b0eb0c87021c75b8 |
completed | April 27, 2026, 10:33 a.m. |
Created at: April 17, 2026, 3:46 p.m.