Triple
T37870869
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lake Pergusa |
E944600
|
entity |
| Predicate | hasBirdMigrationRouteRole |
P74410
|
FINISHED |
| Object | stopover site |
—
|
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: stopover site | Statement: [Lake Pergusa, hasBirdMigrationRouteRole, stopover site]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBirdMigrationRouteRole Context triple: [Lake Pergusa, hasBirdMigrationRouteRole, stopover site]
-
A.
hasMigratoryBirdUse
chosen
Indicates that an entity is used, visited, or relied upon by migratory birds, such as for feeding, resting, or breeding during migration.
-
B.
migratoryBirdsFrom
Indicates a relationship where the subject is a location or region that serves as the origin from which migratory birds travel or disperse.
-
C.
migratoryBehavior
Indicates the pattern, timing, and routes of movement that an entity follows when migrating from one location or region to another.
-
D.
migratoryStatus
Indicates whether an entity regularly moves between different geographic areas according to a recurring (often seasonal) migration pattern.
-
E.
hasBirdColony
Indicates that one entity hosts or contains a colony of birds associated with it.
- 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_69f76eef55d481908ca6660b4b532550 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fcc7338120819081cb46547d60f2cb |
completed | May 7, 2026, 5:09 p.m. |
| PD | Predicate disambiguation | batch_69fcc58566a0819082d5ea36e03bf0c6 |
completed | May 7, 2026, 5:01 p.m. |
Created at: May 3, 2026, 4:19 p.m.