Triple
T27787442
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hamerkop |
E700997
|
entity |
| Predicate | nestEntrance |
P6140
|
FINISHED |
| Object | side entrance tunnel |
—
|
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: side entrance tunnel | Statement: [Hamerkop, nestEntrance, side entrance tunnel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nestEntrance Context triple: [Hamerkop, nestEntrance, side entrance tunnel]
-
A.
hasEntranceOn
Indicates that one entity’s entrance or access point is located on or faces a specified side, boundary, or feature of another entity.
-
B.
hasEntrance
chosen
Indicates that one entity possesses or provides an entry point or access way to another entity or space.
-
C.
nestLocation
Indicates the place or environment where an animal or organism builds or maintains its nest.
-
D.
guardedEntranceTo
Indicates that one entity serves as a protective or controlling barrier for access to another entity’s entrance.
-
E.
hasNarrowEntrance
Indicates that an entity possesses an entrance that is relatively small or restricted in width compared to typical or surrounding access points.
- 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_69ef6a50d8088190acbf3dfbb06d8091 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f637d2e5e08190bc1708336a4fbfc5 |
completed | May 2, 2026, 5:43 p.m. |
| PD | Predicate disambiguation | batch_69f6318ae6f08190b3f85f9201046a15 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 5:26 p.m.