Triple
T24909059
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alfaro |
E623794
|
entity |
| Predicate | hasWildlifeColony |
P153364
|
FINISHED |
| Object | large white stork colony |
—
|
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: large white stork colony | Statement: [Alfaro, hasWildlifeColony, large white stork colony]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWildlifeColony Context triple: [Alfaro, hasWildlifeColony, large white stork colony]
-
A.
hasWildlifeSite
Indicates that a location or entity possesses, contains, or is designated as a wildlife site.
-
B.
hasWildlifeHabitats
Indicates that an entity contains or supports natural environments where wildlife species live, feed, or reproduce.
-
C.
hasWildlifeActivity
Indicates that wildlife is present in the area and engaging in observable behaviors or movements.
-
D.
hasWildlifeStatus
Indicates the conservation or protection status assigned to wildlife associated with an entity.
-
E.
hasMajorWildlife
chosen
Indicates that a location or area supports significant populations or habitats of important wildlife species.
- 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_69e2fac797cc8190b30d77f4121099ac |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f44a417a58819081777e18dda149fd |
completed | May 1, 2026, 6:37 a.m. |
| PD | Predicate disambiguation | batch_69f442b8479c8190a7c8e416ac9e28a0 |
completed | May 1, 2026, 6:05 a.m. |
Created at: April 18, 2026, 5:27 a.m.