Triple
T11017232
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | red knot |
E260393
|
entity |
| Predicate | keyPreyDuringMigration |
P86850
|
FINISHED |
| Object | horseshoe crab eggs |
—
|
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: horseshoe crab eggs | Statement: [red knot, keyPreyDuringMigration, horseshoe crab eggs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keyPreyDuringMigration Context triple: [red knot, keyPreyDuringMigration, horseshoe crab eggs]
-
A.
mainPreySpecies
chosen
Indicates the species that serves as the primary prey or main food source for a given predator.
-
B.
migratoryBehavior
Indicates the pattern, timing, and routes of movement that an entity follows when migrating from one location or region to another.
-
C.
migratoryBirdsFrom
Indicates a relationship where the subject is a location or region that serves as the origin from which migratory birds travel or disperse.
-
D.
hasMigratoryBirdUse
Indicates that an entity is used, visited, or relied upon by migratory birds, such as for feeding, resting, or breeding during migration.
-
E.
preysOn
Indicates that one entity hunts, kills, and consumes another entity as a food source.
- 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_69d6aa9687448190b28d353b1b6a610e |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d797a682908190b061d1995e2866b6 |
completed | April 9, 2026, 12:12 p.m. |
| PD | Predicate disambiguation | batch_69d72e995e008190bbffb314129ed0cd |
completed | April 9, 2026, 4:44 a.m. |
Created at: April 8, 2026, 9:25 p.m.