Triple
T31553616
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barilius |
E805068
|
entity |
| Predicate | preferredCurrent |
P88570
|
FINISHED |
| Object | fast-flowing water |
—
|
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: fast-flowing water | Statement: [Barilius, preferredCurrent, fast-flowing water]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: preferredCurrent Context triple: [Barilius, preferredCurrent, fast-flowing water]
-
A.
currentPreference
chosen
Indicates the option, choice, or setting that an entity presently favors over alternatives at this moment in time.
-
B.
favored
Indicates that one entity is preferred, supported, or given advantage over others by another entity.
-
C.
primaryFor
Indicates that one entity serves as the main or principal option, resource, or association for another entity among possible alternatives.
-
D.
statedPreference
Indicates that one entity has explicitly expressed or declared a preference for another entity or option.
-
E.
preferredStrata
Indicates the geological or social layers that an entity most favors, prioritizes, or tends to occupy or interact with over others.
- 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_69f348d22e088190ad555d5bd42f9da0 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a8055f8081908f635fe04654b5fe |
completed | May 3, 2026, 1:42 a.m. |
| PD | Predicate disambiguation | batch_69f6a75656e081908739ed9e2f600e42 |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 30, 2026, 10:12 p.m.