Triple
T28127198
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lampetra planeri |
E710958
|
entity |
| Predicate | prefersCurrent |
P88570
|
FINISHED |
| Object | moderate to fast-flowing streams |
—
|
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: moderate to fast-flowing streams | Statement: [Lampetra planeri, prefersCurrent, moderate to fast-flowing streams]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: prefersCurrent Context triple: [Lampetra planeri, prefersCurrent, moderate to fast-flowing streams]
-
A.
currentPreference
chosen
Indicates the option, choice, or setting that an entity presently favors over alternatives at this moment in time.
-
B.
statedPreference
Indicates that one entity has explicitly expressed or declared a preference for another entity or option.
-
C.
isPreferredWhen
Indicates that one option, condition, or entity is chosen or favored over others in a particular context or situation.
-
D.
unitPreference
Indicates a relationship where one entity specifies or favors a particular unit of measurement or representation over others.
-
E.
endoPreference
Indicates a preference or tendency for something to occur or be located within the interior or internal part of an entity.
- 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_69ef9b73bd288190a21ae3d6aa14f386 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f6691f5e188190b12c7b2eb729a45e |
completed | May 2, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69f6659b62fc8190b21555d0ba54db2d |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 27, 2026, 9:20 p.m.