Triple
T5556773
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lipotidae |
E145662
|
entity |
| Predicate | evolutionaryAdaptation |
P55597
|
FINISHED |
| Object | freshwater specialization |
—
|
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: freshwater specialization | Statement: [Lipotidae, evolutionaryAdaptation, freshwater specialization]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: evolutionaryAdaptation Context triple: [Lipotidae, evolutionaryAdaptation, freshwater specialization]
-
A.
evolutionaryDescription
chosen
Indicates how an entity has changed, adapted, or developed over time through evolutionary processes.
-
B.
adaptation
Indicates a relationship where one entity changes or is modified to better suit, function within, or correspond to another entity or context.
-
C.
evolutionaryPhase
Indicates the stage or period an entity is in within a broader process of gradual development or evolution.
-
D.
evolves
Indicates that one entity undergoes a process of gradual change or development into another, typically more advanced or different, state or form.
-
E.
adaptationSuccess
Indicates that an entity has effectively adjusted or responded to a change in conditions, environment, or requirements.
- 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_69c008fcaf788190bafa02a1917ee73b |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c01ffe12cc81908186f28ace0f4d82 |
completed | March 22, 2026, 4:59 p.m. |
| PD | Predicate disambiguation | batch_69c01b10bbf8819098655839c03b7832 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:36 p.m.