Triple
T191164
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Straits of Florida |
E3723
|
entity |
| Predicate | isMigrationRouteFor |
P1179
|
FINISHED |
| Object | marine mammals |
—
|
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: marine mammals | Statement: [Straits of Florida, isMigrationRouteFor, marine mammals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMigrationRouteFor Context triple: [Straits of Florida, isMigrationRouteFor, marine mammals]
-
A.
isMajorRouteFor
chosen
Indicates that something serves as a primary or heavily used pathway or channel for the movement or flow of something else.
-
B.
isDestinationFor
Indicates that one entity serves as the endpoint or target location that another entity is intended to reach or be directed toward.
-
C.
followsRouteOf
Indicates that one entity travels along the same path or route that another entity takes or has taken.
-
D.
migrationPattern
Indicates the typical routes, timing, and destinations followed by entities as they move periodically from one location or region to another.
-
E.
hasRoute
Indicates that there exists a path or connection enabling travel or communication from one entity to another.
- 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_69a2548debd48190ae3a06d6e65b53c6 |
completed | Feb. 28, 2026, 2:35 a.m. |
| NER | Named-entity recognition | batch_69a25964fc5c8190bd3e37daaf695ecf |
completed | Feb. 28, 2026, 2:56 a.m. |
| PD | Predicate disambiguation | batch_69a25673ce3c8190b1a3df5b814a0595 |
completed | Feb. 28, 2026, 2:44 a.m. |
Created at: Feb. 28, 2026, 2:41 a.m.