Triple
T9531664
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nemacheilidae |
E229910
|
entity |
| Predicate | currentPreference |
P88570
|
FINISHED |
| Object | fast current |
—
|
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 current | Statement: [Nemacheilidae, currentPreference, fast current]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currentPreference Context triple: [Nemacheilidae, currentPreference, fast current]
-
A.
statedPreference
Indicates that one entity has explicitly expressed or declared a preference for another entity or option.
-
B.
unitPreference
Indicates a relationship where one entity specifies or favors a particular unit of measurement or representation over others.
-
C.
currentPrefect
Indicates that an entity currently holds the position or role of prefect for another entity (such as a school, region, or administrative unit).
-
D.
typicalPolicyPreference
Indicates that one entity’s policy preference is characteristic or representative of what is usually favored by another entity or group.
-
E.
isPreferredWhen
Indicates that one option, condition, or entity is chosen or favored over others in a particular context or situation.
- F. None of above. chosen
Provenance (4 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_69ca8479934c81908006d0e6e970ae05 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd98b408648190a04127c1d47fe7d2 |
completed | April 1, 2026, 10:14 p.m. |
| PD | Predicate disambiguation | batch_69cca56c44f88190a54a5d2a133bb07e |
completed | April 1, 2026, 4:56 a.m. |
| PDg | Predicate description generation | batch_69cca89f1d748190bf3636bea28d8a37 |
completed | April 1, 2026, 5:09 a.m. |
Created at: March 30, 2026, 8 p.m.