Triple
T23320177
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | falua |
E591128
|
entity |
| Predicate | seaConditionAdaptation |
P151859
|
FINISHED |
| Object | strong winds |
—
|
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: strong winds | Statement: [falua, seaConditionAdaptation, strong winds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seaConditionAdaptation Context triple: [falua, seaConditionAdaptation, strong winds]
-
A.
hasSeaCondition
Indicates that an entity is associated with or characterized by a particular state or condition of the sea.
-
B.
seaworthiness
Indicates that something possesses the necessary qualities or condition to be safely and effectively used at sea.
-
C.
waveCondition
Indicates that a specified action, state, or relationship holds only under certain wave-related conditions or patterns.
-
D.
haveBuoyancyAdaptation
Indicates that an entity possesses adaptations or mechanisms that enable it to control or maintain its buoyancy in a fluid environment.
-
E.
touchesSea
Indicates that one entity is in direct physical contact with the sea or coastline of another entity.
- 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_69e25d1effe4819096907f95f610dbff |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1978440888190b316664812105d60 |
completed | April 29, 2026, 5:30 a.m. |
| PD | Predicate disambiguation | batch_69effcf8ca2c8190887d4f4656617d21 |
completed | April 28, 2026, 12:19 a.m. |
| PDg | Predicate description generation | batch_69f01d88b4ec8190a2a17a88e0eda178 |
completed | April 28, 2026, 2:38 a.m. |
Created at: April 17, 2026, 5:07 p.m.