Triple
T28132066
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Morus bassanus |
E711092
|
entity |
| Predicate | foragingHeight |
P14602
|
FINISHED |
| Object | typically 10–40 m above 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: typically 10–40 m above water | Statement: [Morus bassanus, foragingHeight, typically 10–40 m above water]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foragingHeight Context triple: [Morus bassanus, foragingHeight, typically 10–40 m above water]
-
A.
foragingStratum
chosen
Indicates the vertical layer or height within a habitat where an organism typically searches for and obtains its food.
-
B.
foragingTendency
Indicates the degree to which an entity is inclined or likely to engage in searching for and gathering food or resources.
-
C.
hasForagingAbility
Indicates that an entity possesses the capability or skill to search for and obtain food or resources.
-
D.
foragingStrategy
Indicates the method or pattern an organism uses to search for, obtain, and exploit food resources.
-
E.
foragingZone
Indicates the area or region where an entity typically searches for and collects food.
- 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_69ef9b73bd288190a21ae3d6aa14f386 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f6412b8ddc8190bc95eb63bd865ef7 |
completed | May 2, 2026, 6:23 p.m. |
| PD | Predicate disambiguation | batch_69f63c6a8474819091b8c6fe98e3862d |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 9:24 p.m.