Triple
T19052160
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Black eagle |
E466286
|
entity |
| Predicate | hasNestingSite |
P38293
|
FINISHED |
| Object | cliffs |
—
|
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: cliffs | Statement: [Black eagle, hasNestingSite, cliffs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNestingSite Context triple: [Black eagle, hasNestingSite, cliffs]
-
A.
usesNestFor
chosen
Indicates that one entity makes use of another entity specifically as a nest or nesting place.
-
B.
containsSite
Indicates that one entity spatially or structurally includes another entity as a site or location within its bounds.
-
C.
hasNeighboringSite
Indicates that one site is located adjacent to or directly next to another site.
-
D.
hasFindingSite
Indicates that a particular finding, observation, or abnormality is located in or associated with a specific anatomical site.
-
E.
hasHierarchyIn
Indicates that one entity occupies a higher or lower level within an ordered structure or chain of command relative to another entity in a specified context.
- 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_69d8dd040fb881909af2a964f65ad208 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5dc031ff881908e8c68c7aaff3733 |
completed | April 20, 2026, 7:55 a.m. |
| PD | Predicate disambiguation | batch_69e4b99633c8819097988608c278ecf8 |
completed | April 19, 2026, 11:16 a.m. |
Created at: April 10, 2026, 12:03 p.m.