Triple
T14907827
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Levante |
E371180
|
entity |
| Predicate | canReachCondition |
P116627
|
FINISHED |
| Object | gale force |
—
|
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: gale force | Statement: [Levante, canReachCondition, gale force]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canReachCondition Context triple: [Levante, canReachCondition, gale force]
-
A.
canReach
Indicates that one entity is able to access, arrive at, or establish a path to another entity.
-
B.
captureCondition
Indicates the specific circumstances or criteria under which a capture event or action is triggered or considered valid.
-
C.
hasChainCondition
Indicates that one entity is subject to, or satisfies, a specified chain condition imposed or characterized by another entity.
-
D.
targetedCondition
Indicates that an action, intervention, or entity is specifically directed toward affecting, treating, or addressing a particular condition.
-
E.
hasCondition
Indicates that an entity possesses, experiences, or is affected by a particular condition or state.
- 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_69d85cc7ea3481908228b5acb7d06f12 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded61b3c808190b4f6df4e5cb401ad |
completed | April 15, 2026, 12:04 a.m. |
| PD | Predicate disambiguation | batch_69de9a4a14a88190951bb8f4c60bd37b |
completed | April 14, 2026, 7:49 p.m. |
| PDg | Predicate description generation | batch_69deb1a4d8dc8190a4c0841c20f2875f |
completed | April 14, 2026, 9:29 p.m. |
Created at: April 10, 2026, 2:23 a.m.