Triple
T35393934
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cape Clear Bird Observatory |
E1023019
|
entity |
| Predicate | locatedOnMigrationRouteOf |
P181949
|
FINISHED |
| Object | seabirds |
—
|
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: seabirds | Statement: [Cape Clear Bird Observatory, locatedOnMigrationRouteOf, seabirds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedOnMigrationRouteOf Context triple: [Cape Clear Bird Observatory, locatedOnMigrationRouteOf, seabirds]
-
A.
locatedOnRouteTo
Indicates that one entity lies along the path or course taken when traveling from a starting point to a specified destination.
-
B.
isPartOfRoute
Indicates that something (such as a segment, stop, or step) belongs to and is contained within a larger route.
-
C.
isMigrationCorridorFor
chosen
Indicates that one location or route serves as a regular pathway used by a species or population during its migration.
-
D.
locatedAlong
Indicates that one entity is situated adjacent to, or running beside, the length or course of another linear feature (such as a road, river, or railway).
-
E.
locatedOnTrekkingRoute
Indicates that something is situated along or directly on a designated trekking or hiking route.
- 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_69f76df34ba48190bd80f0814cdcd540 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0324d08190ac5b610cc0f6a38c |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:03 p.m.