Triple
T33813339
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iriatherina |
E866597
|
entity |
| Predicate | preferredWaterConditions |
P27141
|
FINISHED |
| Object | soft to moderately hard 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: soft to moderately hard water | Statement: [Iriatherina, preferredWaterConditions, soft to moderately hard water]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: preferredWaterConditions Context triple: [Iriatherina, preferredWaterConditions, soft to moderately hard water]
-
A.
waterCondition
chosen
Indicates the state or quality of water affecting an entity, such as its cleanliness, safety, or suitability for a particular use.
-
B.
prefersWater
Indicates a relationship where an entity favors or chooses water over other available options.
-
C.
hasSnorkelingConditions
Indicates that suitable conditions exist at a location or time for snorkeling to be safely and enjoyably performed.
-
D.
hasWaterCharacteristics
Indicates that one entity possesses qualities, properties, or behaviors characteristic of water.
-
E.
seaConditionAdaptation
Indicates how well an entity adjusts or responds to varying or challenging sea or ocean conditions.
- 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_69f349911a8c81908478662194b23d8c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7051ad6e4819095e82bbd64761803 |
completed | May 3, 2026, 8:19 a.m. |
| PD | Predicate disambiguation | batch_69f700fe24e08190998e2c96fbaaad38 |
completed | May 3, 2026, 8:02 a.m. |
Created at: May 1, 2026, 1:46 a.m.