Triple
T20493872
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cloud 9 |
E502815
|
entity |
| Predicate | breaksOver |
P140299
|
FINISHED |
| Object | coral reef |
—
|
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: coral reef | Statement: [Cloud 9, breaksOver, coral reef]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: breaksOver Context triple: [Cloud 9, breaksOver, coral reef]
-
A.
breaksOn
Indicates that one entity fractures, shatters, or fails when subjected to contact with or force from another entity.
-
B.
breaksWith
Indicates that one entity ends or disrupts an existing association, agreement, or alignment with another entity.
-
C.
breaksBestOn
Indicates that something performs optimally or is most effective when it breaks or is broken under certain conditions or against certain targets.
-
D.
brokenBy
Indicates that one entity causes the damage, destruction, or loss of functionality of another entity.
-
E.
breakType
Indicates the specific kind or category of break or interruption that occurs in a process, activity, or sequence.
- 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_69e0b4b0373881909dd3e9387f82eab4 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e69cbc58d08190bf3f6b60259a8be1 |
completed | April 20, 2026, 9:38 p.m. |
| PD | Predicate disambiguation | batch_69e59fcdf6e08190a604204615dc56e6 |
completed | April 20, 2026, 3:38 a.m. |
| PDg | Predicate description generation | batch_69e5a6a824748190bbe6192d73f3c613 |
completed | April 20, 2026, 4:08 a.m. |
Created at: April 16, 2026, 11:35 a.m.