Triple
T8029981
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eared grebe |
E186951
|
entity |
| Predicate | usesDuringMigration |
P4341
|
FINISHED |
| Object | saline lakes |
—
|
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: saline lakes | Statement: [Eared grebe, usesDuringMigration, saline lakes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesDuringMigration Context triple: [Eared grebe, usesDuringMigration, saline lakes]
-
A.
usedDuring
chosen
Indicates that one entity is employed, applied, or active in the course of another entity’s process, event, or time period.
-
B.
enabledMigrationOf
Indicates that one entity made it possible for another entity to move, transfer, or transition from one state, location, or system to another.
-
C.
associatedWithMigration
Indicates a relationship or connection between entities that is linked to, results from, or occurs in the context of migration.
-
D.
supportsMigrationOf
Indicates that one entity enables, facilitates, or is compatible with the migration or transfer of another entity from one environment, system, or context to another.
-
E.
ownedDuring
Indicates that one entity possessed or held ownership of another entity for some or all of a specified time interval.
- 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_69ca82ad4e2c8190a693e3c9e30fe66f |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3ecf0f2c819091899211003c461e |
completed | March 31, 2026, 3:26 a.m. |
| PD | Predicate disambiguation | batch_69cb049688208190b32088bd2c5930bc |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:22 p.m.